Communication method and communication device
By determining the third network slice based on configuration information in the core network element and using its resources to establish a PDU session, the problem of failed establishment of PDU sessions on the terminal device resides outside the cell is solved, and the session success rate and network stability are improved.
Patent Information
- Application Number
- CN202311425059.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-10-27
- Publication Date
- 2025-04-29
AI Technical Summary
When the resident cell of the terminal device is located outside the service area of the network slice, how to improve the possibility of successful PDU session establishment and avoid service interruptions and delays.
By receiving a request message from the terminal device, the core network element determines based on the configuration information that the cell is located outside the service area of the second network slice, and determines a third network slice from the network slice where available resources are present. The resources configured in the cell are used to establish a second PDU session, providing the same services as the first PDU session.
This improves the possibility of successful PDU session establishment, reduces service interruptions and delays, and ensures that terminal devices can still obtain stable network services when they reside outside the cell.
Smart Images

Figure CN119907143A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present application relate to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art
[0002] With the development of mobile communication technology, various new services and application scenarios continue to emerge. These services have very different requirements for network functions, connection performance and security. If a single network is used to carry these services, it will be difficult to meet the requirements of high bandwidth, low latency, high reliability and so on. In addition, building a new network for each service will bring huge costs. This requires the fifth generation (5G) communication system to be flexible and scalable while being able to meet different business needs. To this end, the 5G communication system provides users with customized network services through end-to-end network slicing.
[0003] Specifically, when the allowed network slice is congested or unavailable on the network side, an alternative network slice is introduced to provide services for the terminal device. Therefore, the terminal device can carry both the single network slice selection assistance information (S-NSSAI) of the allowed network slice and the S-NSSAI of the alternative network slice in the protocol data unit (PDU) session establishment request to establish a PDU session associated with the alternative network slice instead of the PDU session associated with the allowed network slice to provide services for the terminal device.
[0004] However, when the service area of the alternative network slice does not include the resident cell of the terminal device, the PDU session request initiated by the terminal device in the resident cell to establish the alternative network slice association will fail. Therefore, how to improve the possibility of successful PDU session establishment when the resident cell of the terminal device is outside the service area of the network slice has become an urgent problem to be solved. Summary of the invention
[0005] The present application provides a communication method, aiming to improve the possibility of successful PDU session establishment when the resident cell of the terminal device is located outside the service area of the network slice.
[0006] In a first aspect, a communication method is provided. The method may be executed by a core network element, or may be executed by a component of the core network element (eg, a chip or a circuit or a chip system). This application does not limit this.
[0007] The communication method includes: receiving a first request message from a terminal device, the first request message is used to request establishment of a first protocol data unit (PDU) session associated with a first network slice, and the first request message includes an identifier of the first network slice and an identifier of a second network slice; in response to the first request message, determining based on configuration information that a first cell is located outside a service area of the second network slice, and determining at least one network slice in the first cell where there are available resources, the configuration information being used to indicate a service area of a network slice configured within a registration area of the terminal device, the first cell being a resident cell of the terminal device; determining a third network slice from the at least one network slice, the resources configured of the third network slice in the first cell being used to establish a second PDU session, the second PDU session being used to provide the terminal device with the services provided by the first PDU session.
[0008] Based on the above technical solution, the core network element responds to the received first request message, determines based on the configuration information that the first cell is located outside the service area of the second network slice, and determines a third network slice from at least one network slice when there is at least one network slice with available resources in the first cell. The resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session. In the case where the resident cell of the terminal device is outside the service area of the second network slice, by determining that there is a third network slice with available resources, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, the establishment of a PDU session associated with the network slice is achieved, thereby increasing the possibility of successful PDU session establishment and reducing service interruptions and delays.
[0009] In combination with the first aspect, in some implementations of the first aspect, the method also includes: receiving first indication information, the first indication information being used to indicate resource usage of a network slice within at least one tracking area; determining a third network slice from the at least one network slice includes: determining the third network slice from the at least one network slice based on the first indication information.
[0010] Based on the above technical solution, after receiving the first indication information, the core network network element can determine the third network slice from at least one network slice based on the first indication information, thereby improving the accuracy of the core network network element in determining the third network slice.
[0011] In combination with the first aspect, in some implementations of the first aspect, the method also includes: receiving second indication information, the second indication information is used to indicate the determination of the third network slice; determining the third network slice from the at least one network slice includes: determining the third network slice from the at least one network slice based on the first indication information.
[0012] Based on the above technical solution, the core network network element receives second indication information before determining the third network slice from at least one network slice, and the second indication information is used to indicate the determination of the third network slice, so that the core network network element determines the third network slice from at least one network slice in response to the second indication information.
[0013] In combination with the first aspect, in certain implementations of the first aspect, the first network slice corresponds to the second network slice, and when a third network slice is determined from the at least one network slice, the method further includes: updating the network slice corresponding to the first network slice from the second network slice to the third network slice.
[0014] Based on the above technical solution, before receiving the first request message, the core network network element determines that the network slice corresponding to the first network slice is the second network slice. When the third network slice is determined from at least one network slice, the core network network element can update the network slice corresponding to the first network slice from the second network slice to the third network slice, thereby realizing the update of the network slice corresponding to the first network slice.
[0015] In combination with the first aspect, in certain implementations of the first aspect, the second PDU session is a PDU session associated with the third network slice, and the method also includes: sending a first message, wherein the first message is used to request establishment of a PDU session associated with the third network slice.
[0016] Based on the above technical solution, if the above-mentioned second PDU session is a PDU session associated with the third network slice, the core network network element can instruct the access network device to establish a PDU session associated with the third network slice through a first message, thereby indicating the establishment of the PDU session and increasing the possibility of successful establishment of the PDU session.
[0017] In combination with the first aspect, in certain implementations of the first aspect, the second PDU session is a PDU session associated with the second network slice, and the method also includes: sending a second message, the second message is used to request establishment of the second PDU session, the second message includes third indication information, and the third indication information is used to indicate the use of resources configured by the third network slice in the first cell to establish the second PDU session.
[0018] Based on the above technical solution, if the above-mentioned second PDU session is a PDU session associated with the second network slice, the core network network element can instruct the access network device to establish a PDU session associated with the second network slice through a second message, and carry third indication information in the second message, indicating that the resources required to establish the PDU session associated with the second network slice are the resources configured in the first cell of the third network slice, thereby indicating the establishment of the PDU session and increasing the possibility of successful establishment of the PDU session.
[0019] In combination with the first aspect, in certain implementations of the first aspect, the third network slice satisfies at least one of the following conditions: the slice service type SST and / or slice distinction SD of the third network slice are the same as the SST and / or SD of the second network slice; or, the third network slice has available resources in all cells within the registration area of the terminal device; or, the third network slice belongs to the first network slice group, and the first network slice group is associated with one or more network slices; or, the third network slice is the network slice with the most resources configured in the first cell.
[0020] Based on the above technical solution, the third network slice determined by the core network network element can be a network slice that meets different conditions in at least one network slice with available resources in the first cell. Therefore, the core network network element can select a suitable third network slice based on different conditions, thereby improving the flexibility of the solution.
[0021] In a second aspect, a communication method is provided. The method may be executed by an access network device, or may be executed by a component of the access network device (eg, a chip or a circuit or a chip system). This application does not limit this.
[0022] The communication method includes: receiving a second message, the second message is used to request the establishment of a protocol data unit (PDU) session associated with a second network slice, the second message includes third indication information, the third indication information is used to indicate the use of resources configured by the third network slice in the first cell to establish the PDU session associated with the second network slice, the third network slice is determined from the at least one network slice by the core network element based on configuration information when the first cell is outside the service area of the second network slice and there is at least one network slice with available resources in the first cell; establishing a data radio bearer (DRB) associated with the third network slice, the DRB is used to provide air interface data transmission for the terminal device; wherein the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device, and the first cell is the resident cell of the terminal device.
[0023] Based on the above technical solution, the access network device responds to the received second message and determines, according to the third indication information in the second message, that the resources configured by the third network slice in the first cell can be used to establish a PDU session associated with the second network slice. Therefore, when the first cell is located outside the service area of the second network slice and there are at least one network slice with available resources in the first cell, the resources of the third network slice with available resources can be used to establish the PDU session associated with the second network slice, thereby realizing the establishment of the PDU session associated with the network slice and improving the possibility of successful establishment of the PDU session.
[0024] In combination with the second aspect, in some implementations of the second aspect, the method also includes: controlling the data transmission rate based on any one of the slice maximum bit rate SMBR of the first network slice, the SMBR of the second network slice, or the SMBR of the third network slice, wherein the first network slice and the second network slice correspond to each other.
[0025] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: sending first indication information, where the first indication information is used to indicate resource usage of a network slice within at least one tracking area.
[0026] Based on the above technical solution, when the access network device is configured (for example, configured by operation administration and maintenance (OAM)) with a service area for one or more network slices, the access network device can provide the core network network element with resource usage of the network slices in at least one tracking area through a first indication information, in order to assist the core network network element to more accurately determine the above-mentioned third network slice.
[0027] In a third aspect, a communication method is provided. The method may be executed by a terminal device, or may be executed by a component of the terminal device (eg, a chip or a circuit or a chip system). This application does not limit this.
[0028] The communication method includes: receiving fourth indication information and configuration information, the fourth indication information is used to indicate that the first network slice corresponds to the second network slice, and the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device; the terminal device determines that when a first protocol data unit PDU session request for establishing the first network slice association is initiated in the first cell, based on the fourth indication information and the configuration information, the first cell is located outside the service area of the second network slice, and determines that there is at least one network slice with available resources in the first cell, and the first cell is the resident cell of the terminal device; sending second indication information, the second indication information is used to indicate a third network slice in the at least one network slice, or the second indication information is used to indicate the determination of the third network slice, wherein the resources configured in the first cell for the third network slice are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session.
[0029] Based on the above technical solution, when the terminal device determines that in the first cell initiates a request for establishing a first PDU session associated with the first network slice, the terminal device can determine based on the received information (such as the fourth indication information and the configuration information): the first cell is located outside the service area of the second network slice corresponding to the first network slice, and there is at least one network slice with available resources in the first cell. Further, the terminal device indicates a third network slice in at least one network slice through the second indication information, or instructs the network side (such as an access network device or a core network element) to determine a third network slice, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session. In the case where the resident cell of the terminal device is outside the service area of the second network slice, by determining that there is a third network slice with available resources, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, the establishment of a PDU session associated with the network slice is achieved, thereby increasing the possibility of successful PDU session establishment and reducing service interruption and latency.
[0030] In combination with the third aspect, in certain implementations of the third aspect, when the second indication information is used to indicate a third network slice in the at least one network slice, the method also includes: determining a third network slice from the at least one network slice.
[0031] Based on the above technical solution, if the second indication information directly indicates a third network slice in at least one network slice, the terminal device determines to obtain the third network slice by itself before sending the second indication information to the network side, thereby eliminating the need for the network side device (such as an access network device or a core network element) to determine the third network slice, thereby reducing the complexity of the network side device.
[0032] In combination with the third aspect, in certain implementations of the third aspect, the second indication information is also used to indicate that the network slice corresponding to the first network slice is updated from the second network slice to the third network slice.
[0033] Based on the above technical solution, the above-mentioned second indication information can also be used to indicate that the network slice corresponding to the first network slice is updated from the second network slice to the third network slice, so that the PDU session associated with the third network slice can be directly established during the subsequent PDU session establishment process, thereby avoiding the failure of establishing the PDU session associated with the second network slice.
[0034] In combination with the third aspect, in certain implementations of the third aspect, the third network slice satisfies at least one of the following conditions: the slice service type SST and / or slice distinction SD of the third network slice are the same as the SST and / or SD of the second network slice; or, the third network slice has available resources in all cells within the registration area of the terminal device; or, the third network slice belongs to the first network slice group, and the first network slice group is associated with one or more network slices; or, the third network slice is the network slice with the most resources configured in the first cell.
[0035] Based on the above technical solution, the third network slice determined by the terminal device or the network side device can be a network slice that meets different conditions in at least one network slice with available resources in the first cell. Therefore, the terminal device or the network side device can select a suitable third network slice based on different conditions, thereby improving the flexibility of the solution.
[0036] In a fourth aspect, a communication method is provided. The method may be performed by an access network device or a core network element, or may be performed by a component (such as a chip or a circuit or a chip system) of the access network device or the core network element. This application does not limit this.
[0037] The communication method includes: receiving second indication information, wherein the second indication information is used to indicate a third network slice, or the second indication information is used to indicate the determination of the third network slice, wherein the third network slice is a network slice in which available resources exist in the first cell; determining the third network slice in response to the second indication information, wherein the resources configured by the third network slice in the first cell are used to establish a second protocol data unit PDU session, wherein the second PDU session is used to provide the terminal device with the services provided by the first PDU session, wherein the first cell is located outside the service area of the second network slice, the first PDU session is a PDU session associated with the first network slice requested to be established by the terminal device, the first network slice corresponds to the second network slice, and the first cell is a resident cell of the terminal device.
[0038] Based on the above technical solution, when the network side device (such as an access network device or a core network element) receives the second indication information, it can determine the third network slice in response to the second indication information. For example, when the second indication information indicates the third network slice, the network side device directly obtains the third network slice based on the second indication information. For example, when the second indication information indicates that the network side device determines the third network slice, the network side device selects a suitable network slice as the third network slice in response to the triggering of the second indication information. The resources configured in the first cell of the third network slice are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session. In the case where the resident cell of the terminal device is outside the service area of the second network slice, by determining that there is a third network slice with available resources, and the resources configured in the first cell of the third network slice are used to establish the second PDU session, the establishment of the PDU session associated with the network slice is achieved, thereby increasing the possibility of successful establishment of the PDU session.
[0039] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the second indication information is used to indicate the determination of the third network slice, the method also includes: determining that the first cell is located outside the service area of the second network slice based on the configuration information, and determining at least one network slice in the first cell where there are available resources, the configuration information being used to indicate the service area of the network slice configured within the registration area of the terminal device; and determining the third network slice from the at least one network slice.
[0040] Based on the above technical solution, when the above-mentioned second indication information is used to indicate the determination of the third network slice, the network side device can determine the third network slice from at least one network slice based on the configuration information that the first cell is located outside the service area of the second network slice, and there is at least one network slice with available resources in the first cell.
[0041] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method also includes: updating the network slice corresponding to the first network slice from the second network slice to the third network slice.
[0042] Based on the above technical solution, the network side device may be a core network network element. If the above second indication information indicates that the core network element determines the third network slice, the core network element may update the network slice corresponding to the first network slice from the second network slice to the third network slice when determining the third network slice, so that in the subsequent PDU session establishment process, the PDU session associated with the third network slice can be directly established, thereby avoiding the failure of establishing the PDU session associated with the second network slice.
[0043] In combination with the fourth aspect, in certain implementations of the fourth aspect, the second PDU session is a PDU session associated with the second network slice, and the method also includes: sending a second message, the second message is used to request establishment of the second PDU session, the second message includes third indication information, and the third indication information is used to indicate the use of resources configured by the third network slice in the first cell to establish the second PDU session.
[0044] Based on the above technical solution, the network side device may be a core network network element. If the above-mentioned second PDU session is a PDU session associated with the second network slice, the core network element may instruct the access network device to establish a PDU session associated with the second network slice through a second message, and carry third indication information in the second message, indicating that the resources required to establish the PDU session associated with the second network slice are the resources configured in the first cell of the third network slice, thereby indicating the establishment of the PDU session and increasing the possibility of successful establishment of the PDU session.
[0045] In combination with the fourth aspect, in certain implementations of the fourth aspect, the second indication information is also used to indicate that the network slice corresponding to the first network slice is updated from the second network slice to the third network slice, and the second PDU session is the PDU session associated with the third network slice. The method also includes: sending a first message, and the first message is used to request to establish a PDU session associated with the third network slice.
[0046] Based on the above technical solution, the network side device may be a core network network element. If the above-mentioned second PDU session is a PDU session associated with the third network slice, the core network element may instruct the access network device through a first message to establish a PDU session associated with the third network slice, thereby indicating the establishment of the PDU session and improving the possibility of successful establishment of the PDU session.
[0047] In combination with the fourth aspect, in certain implementations of the fourth aspect, the method also includes: establishing a data radio bearer DRB associated with the third network slice, and the DRB is used to provide air interface data transmission for the terminal device.
[0048] Based on the above technical solution, the network side device may be an access network device. After the access network device determines the third network slice, it may establish a DRB associated with the third network slice to provide air interface data transmission for the terminal device.
[0049] In a fifth aspect, a communication method is provided. The method may be executed by a terminal device, or may be executed by a component of the terminal device (eg, a chip or a circuit or a chip system). This application does not limit this.
[0050] The communication method includes: receiving fourth indication information and configuration information, the fourth indication information is used to indicate that the first network slice corresponds to the second network slice, and the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device; when the terminal device determines that the first cell is outside the service area of the second network slice based on the third indication information and the configuration information, the terminal device does not initiate a first protocol data unit PDU session request to establish the first network slice association within the first cell.
[0051] Based on the above technical solution, the terminal device can determine based on the received information (such as the fourth indication information and the configuration information) that the first cell is located outside the service area of the second network slice corresponding to the first network slice. In this case, the terminal device can determine not to initiate a first PDU session request for establishing the first network slice association in the first cell, thereby avoiding subsequent PDU session establishment failures and unnecessary resource overhead.
[0052] In a sixth aspect, a communication method is provided. The method may be executed by an access network device, or may be executed by a component of the access network device (eg, a chip or a circuit or a chip system). This application does not limit this.
[0053] The communication method includes: receiving a second request message, the second request message is used to request to establish a protocol data unit PDU session associated with a second network slice in a first cell; determining based on configuration information that the first cell is outside the service area of the second network slice, and determining at least one network slice in the first cell where there are available resources, the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device; establishing a data radio bearer DRB associated with a third network slice in the at least one network slice, the DRB is used to provide air interface data transmission for the terminal device; wherein the first cell is a resident cell of the terminal device, the first cell is outside the service area of the second network slice, and the resources configured by the third network slice in the first cell are used to establish a PDU session associated with the second network slice.
[0054] Based on the above technical solution, the access network device responds to the received second request message and determines based on the configuration information that: the first cell is located outside the service area of the second network slice corresponding to the first network slice, and there is at least one network slice with available resources in the first cell. Therefore, in the process of establishing the DRB, the access network device can establish a DRB associated with the third network slice instead of the DRB associated with the second network slice, use the resources of the third network slice with available resources, establish a PDU session associated with the network slice, and realize the establishment of the PDU session associated with the network slice, thereby increasing the possibility of successful establishment of the PDU session and reducing service interruption and delay.
[0055] In combination with the sixth aspect, in certain implementations of the sixth aspect, the method also includes: determining the third network slice from the at least one network slice.
[0056] Based on the above technical solution, the access network device can determine and obtain the third network slice by itself, thereby eliminating the need for the core network network element to determine the third network slice, thereby reducing the complexity of the core network network elements.
[0057] In combination with the sixth aspect, in certain implementations of the sixth aspect, the method also includes: sending fifth indication information, wherein the fifth indication information is used to indicate the third network slice, or the fifth indication information is used to indicate the determination of the third network slice.
[0058] Based on the above technical solution, the access network device can instruct the core network network element to determine the above-mentioned third network slice through the fifth indication information, and then the core network network element instructs to use the resources configured in the first cell with the third network slice to establish a second PDU session. The access network device does not need to determine the third network slice by itself, thereby reducing the complexity of the access network device; or, the access network device can determine the third network slice by itself, thereby eliminating the need for the core network network element to determine the third network slice, thereby reducing the complexity of the core network network element.
[0059] In combination with the sixth aspect, in certain implementations of the sixth aspect, the fifth indication information is also used to indicate that the network slice corresponding to the first network slice is updated from the second network slice to the third network slice.
[0060] Based on the above technical solution, the fifth indication information can be used to indicate that the network slice corresponding to the first network slice is updated from the second network slice to the third network slice, or the core network element can automatically update the network slice corresponding to the first network slice from the second network slice to the third network slice after determining the third network slice, without the need for additional indication of the fifth indication information. Therefore, in the subsequent PDU session establishment process, the PDU session associated with the third network slice can be directly established, avoiding the failure of the PDU session establishment associated with the second network slice.
[0061] In combination with the sixth aspect, in certain implementations of the sixth aspect, the method further includes: controlling the data transmission rate based on any one of the slice maximum bit rate SMBR of the first network slice, the SMBR of the second network slice, or the SMBR of the third network slice, wherein the first network slice and the second network slice correspond to each other.
[0062] In combination with the sixth aspect, in certain implementations of the sixth aspect, the method also includes: sending first indication information, wherein the first indication information is used to indicate resource usage of a network slice within at least one tracking area.
[0063] Based on the above technical solution, when the access network device is configured (for example, configured by OAM) with a service area for one or more network slices, the access network device can provide the core network network element with resource usage of the network slices within at least one tracking area through a first indication information, in order to assist the core network network element to more accurately determine the above-mentioned third network slice.
[0064] In combination with the sixth aspect, in certain implementations of the sixth aspect, the third network slice satisfies at least one of the following conditions: the slice service type SST and / or slice distinction SD of the third network slice are the same as the SST and / or SD of the second network slice; or, the third network slice has available resources in all cells within the registration area of the terminal device; or, the third network slice belongs to the first network slice group, and the first network slice group is associated with one or more network slices; or, the third network slice is the network slice with the most resources configured in the first cell.
[0065] Based on the above technical solution, the third network slice determined by the network side device can be a network slice that meets different conditions in at least one network slice with available resources in the first cell. Therefore, the network side device can select a suitable third network slice based on different conditions, thereby improving the flexibility of the solution.
[0066] In a seventh aspect, a communication device is provided. The communication device may be a first device, or a module or unit (e.g., a chip, or a chip system, or a circuit) in the first device that corresponds to the method / operation / step / action described in the first to sixth aspects and any one of their embodiments, or may be used in combination with the first device.
[0067] Exemplarily, the first device may be the core network element or a component of a core network element (such as a chip or circuit or chip system) of the first aspect mentioned above, and the first device includes a transceiver module or unit for performing the transceiver operations / steps / actions described in the first aspect and any one of its embodiments, and a processing module or unit for performing the processing operations / steps / actions described in the first aspect and any one of its embodiments.
[0068] Exemplarily, the first device may be the access network device or a component of the access network device (such as a chip or circuit or a chip system) of the second aspect or the sixth aspect mentioned above, and the first device includes a transceiver module or unit for performing the transceiver operation / step / action described in the second aspect or the sixth aspect and any one of its embodiments, and includes a processing module or unit for performing the processing operation / step / action described in the second aspect or the sixth aspect and any one of its embodiments. Exemplarily, the first device may be the terminal device or a component of the terminal device (such as a chip or circuit or a chip system) of the third aspect or the fifth aspect mentioned above, and the first device includes a transceiver module or unit for performing the transceiver operation / step / action described in the third aspect or the fifth aspect and any one of its embodiments, and includes a processing module or unit for performing the processing operation / step / action described in the third aspect or the fifth aspect and any one of its embodiments.
[0069] Exemplarily, the first device may be the access network device or core network element of the fourth aspect mentioned above, or a component of the access network device or core network element (such as a chip or circuit or chip system), and the first device includes a transceiver module or unit for performing the transceiver operations / steps / actions described in the fourth aspect and any one of its embodiments, and a processing module or unit for performing the processing operations / steps / actions described in the fourth aspect and any one of its embodiments.
[0070] In an eighth aspect, a communication device is provided. The communication device is used to execute the method provided in the first to sixth aspects and any one of the embodiments thereof. Specifically, the communication device may include a unit and / or module (e.g., a processing unit, a transceiver unit) for executing the method provided in the first to sixth aspects and any one of the embodiments thereof.
[0071] In one implementation, the communication device is a device. The transceiver unit may be a transceiver, or an input / output interface. The processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.
[0072] In another implementation, the communication device may be a chip, a chip system or a circuit in a device. In this case, the transceiver unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit.
[0073] In a ninth aspect, the present application provides a processor for executing the methods provided in the first to sixth aspects above.
[0074] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or unless they conflict with their actual function or internal logic in the relevant description, they can be understood as operations such as processor output, reception, input, etc., or as sending and receiving operations performed by the radio frequency circuit and antenna, and this application does not limit this.
[0075] In a tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed on a communication device, the communication device executes a method in any one of the implementation modes of the first to sixth aspects.
[0076] In an eleventh aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is caused to execute the method provided in any one of the implementations of the first to sixth aspects.
[0077] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface, the processor reads instructions through the communication interface and executes the method provided by any one of the implementation modes of the first to sixth aspects above.
[0078] Optionally, as an implementation method, the chip also includes a memory, the memory stores a computer program or instructions, and the processor is used to execute the computer program or instructions stored in the memory. When the computer program or instructions are executed, the processor is used to execute the method provided in any one of the implementation methods of the first to sixth aspects above.
[0079] In a thirteenth aspect, a communication system is provided, comprising a core network element for executing a method of any one of the implementation modes of the first aspect and an access network device for executing a method of any one of the implementation modes of the second aspect.
[0080] In a fourteenth aspect, a communication system is provided, comprising a terminal device for executing a method of any one of the implementation modes of the third aspect and a network side device for executing a method of any one of the implementation modes of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0081] Figure 1 It is a schematic diagram of a communication system 100 to which an embodiment of the present application is applicable.
[0082] Figure 2 This is a schematic diagram of the network slicing service area provided by this application.
[0083] Figure 3 This is a schematic diagram of a scenario in which a PDU session establishment fails provided by this application.
[0084] Figure 4 It is a schematic flow chart of a communication method provided by the present application.
[0085] Figure 5 It is a schematic flow chart of another communication method provided by the present application.
[0086] Figure 6 It is a schematic flow chart of another communication method provided by the present application.
[0087] Figure 7 It is a schematic block diagram of a communication device 10 provided in an embodiment of the present application.
[0088] Figure 8 It is a schematic diagram of another communication device 20 provided in an embodiment of the present application.
[0089] Fig. 9 It is a schematic diagram of a chip system 30 provided in an embodiment of the present application. DETAILED DESCRIPTION
[0090] In order to facilitate understanding of the embodiments of the present application, the following explanations are made.
[0091] First, in this application, "used for indication" may include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used for indicating A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that A must be included in the indication information.
[0092] The information indicated by the indication information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. The information to be indicated can be sent as a whole, or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in this application. Among them, the sending period and / or sending time of these sub-information can be pre-defined, for example, pre-defined according to the protocol, or can be configured by the transmitting end device by sending configuration information to the receiving end device.
[0093] Second, "at least one" shown in the present application refers to one or more, and "multiple" refers to two or more. In addition, in the embodiments of the present application, "first", "second" and various digital numbers (for example, "#1", "#2", etc.) are only for the convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of each process below does not mean the order of execution, and the execution order of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. It should be understood that the objects described in this way can be interchanged in appropriate circumstances, so that the schemes outside the embodiments of the present application can be described. In addition, in the embodiments of the present application, the words "410", "420" and the like are only for the convenience of description, and the order of execution steps is not limited.
[0094] Third, in this application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific way.
[0095] Fourth, the "storage" involved in the embodiments of the present application may refer to storage in one or more memories. The one or more memories may be separately set or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially separately set and partially integrated in a decoder, a processor, or a communication device. The type of memory may be any form of storage medium, which is not limited by the present application.
[0096] Fifth, the “protocol” involved in the embodiments of the present application may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, which is not limited in the present application.
[0097] Sixth, in the embodiments of the present application, "under the circumstances", "when", and "if" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are the same.
[0098] Seventh, in the embodiments of the present application, various terms and English abbreviations, such as radio resource control (RRC), etc., are illustrative examples given for the convenience of description and should not constitute any limitation to the present application. The present application does not exclude the possibility of defining other terms that can achieve the same or similar functions in existing or future protocols.
[0099] Eighth, the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0100] The technical solution in this application will be described below in conjunction with the accompanying drawings.
[0101] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions of the embodiments of the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of things (IoT) communication system or other communication systems.
[0102] To facilitate understanding of the embodiments of the present application, first Figure 1 The communication system shown in the figure is used as an example to describe in detail the communication system applicable to the embodiments of the present application. Figure 1 1 is a schematic diagram of a communication system 100 to which the present application embodiment is applicable. Figure 1 As shown, the communication system 100 may include at least one access network device, such as Figure 1 The access network device 110 shown; the communication system 100 may also include at least one terminal device, such as Figure 1 The terminal device 120 shown; the communication system 100 may also include at least one core network (CN) device, such as Figure 1 The core network device 130 shown. The access network device 110 and the terminal device 120 can communicate via a wireless link, and the access network device 110 and the core network device 130 can communicate via a wireless link. Each communication device, such as the access network device 110, the terminal device 120 and the core network device 130, can be configured with multiple antennas. For each communication device in the communication system 100, the configured multiple antennas may include at least one transmitting antenna for sending signals and at least one receiving antenna for receiving signals. Therefore, the communication devices in the communication system 100, such as the access network device 110 and the terminal device 120, can communicate through multi-antenna technology.
[0103] By way of example and not limitation, Figure 1The access network device and the terminal device in the scenario shown can communicate in a variety of ways, such as communication between the access network device and the terminal device through a point-to-point transmission method, communication between the access network device and the terminal device through a multi-hop (or relay) transmission method, and communication between multiple access network devices and terminal devices through dual connectivity (dual connectivity, DC) or multi-connection transmission methods. In the embodiments of the present application, no limitation is imposed on the communication method between the access network device and the terminal device. For example, the transmission between the access network device and the terminal device can be uplink, downlink, access link, backhaul link or sidelink, etc.
[0104] The terminal equipment in the embodiments of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, a user equipment (UE), a terminal, a wireless communication device, a user agent or a user device. The terminal equipment may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved public land mobile communication network (PLMN), etc., and the embodiments of the present application are not limited to this.
[0105] As an example and not a limitation, in the embodiments of the present application, wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
[0106] In addition, in the embodiment of the present application, the terminal device can also be a terminal device in an IoT system, whose main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. In the embodiment of the present application, IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.
[0107] The access network device in the embodiment of the present application can be any device with wireless transceiver function used to communicate with the terminal device. The device includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB (HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., and can also be a gNB in 5G, such as NR, system, or a transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DBU). unit, DU), etc., and can also be a device in the 6G system that communicates with the terminal device, such as the gNB in the 6G system.
[0108] In some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by the DU+AAU. It can be understood that the access network device can be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as a network device in an access network (radio access network, RAN), or the CU may be classified as a network device in a core network (core network, CN), which is not limited in the present application.
[0109] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, the radio access network may also be an ORAN architecture. In the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. Any unit in the CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0110] The core network equipment part in the embodiment of the present application may include but is not limited to the following NFs: user plane function (UPF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management function (UDM), unified data repository function (UDR), network data analysis function (NWDAF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), network slice selection function (NSSF), etc. Among them, AMF, SMF, UPF, NEF, AUSF, NRF, PCF, NSSF, and UDM can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.
[0111] It should be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, or may use other names.
[0112] As an example but not a limitation, in an embodiment of the present application, the CN device is used to provide user connection, user management, and service carrying, and provides an interface to the external network as a bearer network. This application mainly involves the AMF network element (or AMF, AMF device, AMF unit, etc.) in the core network. AMF is a control plane network function provided by the operator network, which is responsible for the access control and mobility management of terminal devices accessing the operator network, such as mobile status management, allocation of user temporary identity, authentication and authorization of users, etc.
[0113] In an embodiment of the present application, a terminal device, an access network device or a core network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU) and a memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system or a windows operating system. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as it can communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application can be a terminal device or a network device, or a functional module in a terminal device or a network device that can call and execute a program.
[0114] In addition, various aspects or features of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable media can include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.
[0115] It should be understood that Figure 1 This article takes the communication between access network equipment and terminal equipment, and between access network equipment and core network equipment as an example to simply illustrate a communication scenario to which this application can be applied, and does not limit other scenarios to which this application can be applied. It should also be understood that Figure 1 This is a simplified schematic diagram for ease of understanding only. The communication system may also include other network devices or other terminal devices. Figure 1 Not drawn in.
[0116] To facilitate understanding of the embodiments of the present application, some basic concepts involved in the present application are briefly described. It should be understood that the basic concepts introduced below are illustrated by taking the basic concepts specified in the NR protocol as an example, but the embodiments of the present application are not limited to the NR system. Therefore, the standard names that appear when describing the NR system as an example are all functional descriptions, and the specific names are not limited. They only indicate the functions of the device and can be correspondingly extended to other systems in the future.
[0117] 1. Network slicing: With the development of mobile communication technology, various new services and application scenarios continue to emerge. These services have very different requirements for network functions, connection performance and security. If a single network is used to carry these services, it will be difficult to meet the requirements of high bandwidth, low latency, high reliability and so on. In addition, building a new network for each service will bring huge costs. This requires 5G to be flexible and scalable while being able to meet different business needs. To this end, 5G provides users with customized network services through end-to-end network slicing (also referred to as "slicing"). Through flexible allocation of network resources and on-demand networking, 5G virtualizes multiple logical subnets with different characteristics and isolation from each other on the same set of physical facilities to provide targeted services to users.
[0118] Different logical subnets are identified and distinguished by single network slice selection assistance information (S-NSSAI).
[0119] Exemplarily, each S-NSSAI may include the following:
[0120] 1) Slice service type (SST): used to point to slice-specific features and service types;
[0121] 2) Slice Differentiator (SD): As a supplement to SST, it can further distinguish multiple network slice instances that meet the same SST. The SD is an optional content of S-NSSAI.
[0122] It should be understood that NSSAI hereinafter refers to one or more S-NSSAIs (ie, S-NSSAI lists).
[0123] For NSSAI, there are several specific categories:
[0124] 1) Subscribed NSSAI: Subscription data belonging to the user;
[0125] 2) Default NSSAI: According to the operator's policy, one or more of the user's subscribed NSSAIs may be set as the default NSSAI; if the UE does not carry an allowed NSSAI in the registration request message, and if the default NSSAI exists, the network can use the default NSSAI to provide services to the UE.
[0126] 3) Requested NSSAI: refers to the allowedNSSAI or configured NSSAI (configured NSSAI) carried by the UE in the registration request message.
[0127] 4) allowed NSSAI: indicates which S-NSSAI among the NSSAI requested by the UE are allowed by the network. The network can indicate the allowed NSSAI to the UE through the "allowed NSSAI" information element (IE) in the registration accept message.
[0128] 5) configured NSSAI: refers to the NSSAI that the network configures for the UE to use. After receiving the configuration parameter indicating the configured NSSAI, the UE learns which S-NSSAI are available in the network based on the configuration parameter. The network can indicate the configured NSSAI to the UE through the "configured NSSAI" IE in the registration accept.
[0129] Specifically, the slice list supported by the access network device is pre-configured by operation, administration and maintenance (OAM) according to the tracking area (TA) granularity, that is, all cells in a specific TA support the same slices. Exemplarily, a TA includes one or more cells. The access network device can report the slice list to the core network when establishing a communication interface (such as an NG interface) with the core network. If the access network device can also support CU / DU separation, the DU sends the slice list supported by each TA to the CU, and the CU reports it to the core network.
[0130] 2. Slice-associated PDU session management: When a UE that has signed up for a slice service initially accesses the network, it can carry the requested NSSAI in the RRC Setup Complete message to initiate a registration request for a specific network slice. The registration request is transparently transmitted to the core network side via the access network device (that is, the access network device does not parse the registration request). The core network then determines whether the network side (including the RAN side and the core network side) can provide services for the slice service based on the UE's subscription information in the UDM (such as subscribed NSSAI).
[0131] If the core network confirms that the current network can support the service corresponding to the requested NSSAI, it will return the allowed NSSAI and the UE's registration area (RA) range (represented by a tracking area identity (TAI) list) to the UE through a registration accept message.
[0132] If the core network confirms that the current network cannot support some or all of the S-NSSAI in the requested NSSAI, it will return the allowed NSSAI and / or rejected NSSAI (i.e. the S-NSSAI(s) in the requested NSSAI that cannot be supported by the current network) and the RA range of the UE to the UE through the registration accept message. When the UE moves within the RA range, it cannot re-initiate a registration request for the rejected NSSAI.
[0133] The UE can initiate a PDU session establishment request to the core network based on the allowed NSSAI (the PDU session establishment request can be carried by the NAS message transparently transmitted by the access network device). After the core network determines that it can support the PDU session, it will send a PDU session resource establishment request to the access network device, where one PDU session is associated with one S-NSSAI. After the access network device determines that resources can be configured for the current PDU session, it will create at least one corresponding data radio bearer (DRB) in the air interface.
[0134] 3. Network slice as group (NSAG): The access network device can notify the UE of the cell reselection priority and specific random access parameters for the slice by broadcasting. The above information is respectively included in the system information block 16 (SIB16) and SIB1. Considering that the broadcast based on slice granularity may bring relatively large overhead to SIB, the concept of network slice group (or NSAG) is proposed, that is, one or more network slices are grouped and identified. Specifically, one or more S-NSSAIs can be mapped to obtain a specific NSAG ID, and the mapping relationship between NSAG ID and S-NSSAI is unique in a specific area.
[0135] Exemplarily, the characteristics of the mapping relationship between NSAG ID and S-NSSAI in a specific area are as follows:
[0136] 1) Bidirectional mapping, including the ID value of NSAG and the mapping value of the associated S-NSSAI;
[0137] 2) OAM configures it to gNB, which sends it to CN via NG interface and CN provides it to UE via NAS message;
[0138] 3) The granularity of regional validity is TA. When the CN sends the mapping relationship of NSAG to the UE through a NAS message, it can also carry the TAI corresponding to the effective mapping relationship;
[0139] 4) Allow network slices not to be associated with any NSAG;
[0140] 5) A network slice can be associated with NSAGs of different purposes, that is, different purposes can have their own independent mapping relationship between NSAG and network slice. For example, network slice #1 can be associated with NSAG #1 for cell reselection and NSAG #2 for random access at the same time. However, for the same purpose, a network slice is not allowed to be associated with multiple NSAGs. For example, when used for cell reselection, network slice #1 is associated with NSAG #1. Similarly, when used for random access, network slice #1 is associated with NSAG #2.
[0141] 6) A corresponding NSAG priority may be configured for each NSAG.
[0142] 4. Slice maximum bit rate (SMBR): The subscription information of the UE may include the UE-slice-MBR. When the gNB receives the UE-slice-MBR associated with the allowed NSSAI from the AMF, the gNB may perform aggregate rate limiting based on the value for one or more activated PDU sessions of the user plane associated with the same slice of the same UE. Specifically, the gNB shall ensure that the aggregate bit rate of all guaranteed bit rate (GBR) and Non-GBR quality of service (QoS) flows belonging to these PDU sessions does not exceed the UE-Slice-MBR, while always ensuring the guaranteed flow bit rate (GFBR) of each GBR QoS flow of these PDU sessions.
[0143] 5. Alternative S-NSSAI: Alternative S-NSSAI is used to provide services to UEs instead of the allowed S-NSSAI with no resources or congested resources on the CN side. It has the following features:
[0144] 1) Alternative S-NSSAI can be supported in UE RA.
[0145] 2) When the UE indicates support for alternative S-NSSAI capability, if an allowed S-NSSAI (i.e. original S-NSSAI) is not available or congested at the CN, the AMF may send the correspondence between the alternative S-NSSAI and the original S-NSSAI to the UE.
[0146] 3) The correspondence may also be sent to the UE in advance, that is, it is not necessarily necessary to rely on establishing the PDU session of the original S-NSSAI to trigger the sending of the correspondence.
[0147] 4) After receiving the corresponding relationship, if the UE needs to initiate a PDU session establishment based on the original network slice, it needs to carry both the original S-NSSAI and the alternative S-NSSAI in the PDU session establishment request. After receiving the PDU session establishment request, the AMF will send both S-NSSAIs to the SMF, and the SMF will determine to establish a PDU session associated with the Alternative S-NSSAI, thus completing the network slice replacement process.
[0148] 5) After completing the network slice replacement, if the alternative S-NSSAI is not the configured NSSAI of the UE, the AMF shall add the alternative S-NSSAI to the configured NSSAI and update the NSAG information (including NSAG priority) associated with the alternative to the UE.
[0149] 6. Network slice area of service (NS-AoS): Consider that when slices are deployed and decommissioned within a certain time interval, the UE and network configuration may be affected. For example, when a slice is no longer available or becomes available, this may affect the allowed NSSAI and other parameters, and the RA may also need to be changed. Figure 2 For example, the TA identified by TAC#1 supports network slice #2, and there are a total of 4 cells in the TA. Due to deployment and other reasons, the resources configured for network slice #2 in Cell#2 are suddenly limited, which means that no resources are configured for network slice #2 in Cell#2, so Cell#2 cannot actually provide network slice #2 services to the UE. In order to avoid affecting the UE and the network side, NS-AoS is introduced to indicate the service area for a specific slice (an area consisting of one or more cells), with the following characteristics:
[0150] 1) NS-AoS is deployed on the RAN side, and AMF can obtain the NS-AoS configured for each slice in the UE RA through OAM;
[0151] 2) When the UE indicates support for NS-AoS capability, the AMF shall send NS-AoS with configured NSSAI to the UE via a registration accept or UE configuration update message;
[0152] 3) After the UE receives the NS-AoS with configured NSSAI, if it initiates a request to establish a PDU session associated with a specific slice in an area outside the NS-AoS for the specific slice within the RA, the UE cannot activate its data plane after the PDU session is established, that is, the PDU session will be retained on the CN side, but no user data will be exchanged between the UE and the CN.
[0153] Combination of the above Figure 1 The present invention briefly introduces the scenarios in which the communication method provided in the embodiments of the present application can be applied, as well as the basic concepts that may be involved in the embodiments of the present application. In the basic concepts, alternative S-NSSAI and NS-AoS are introduced. It should be understood that after the AMF sends the correspondence between the original S-NSSAI and the alternative S-NSSAI to the UE residing in the NS-AoS of the original S-NSSAI, the UE moves to a cell outside the NS-AoS of the alternative S-NSSAI to initiate a PDU session associated with the original network slice and trigger network slice replacement (because the original S-NSSAI has no resources configured on the CN side). When it is necessary to establish a PDU session associated with the alternative S-NSSAI, the RAN side has no resources configured for the alternative S-NSSAI, and therefore the PDU session associated with the alternative S-NSSAI cannot be successfully established.
[0154] To facilitate understanding, the possible problems of combining the above alternative S-NSSAI and NS-AoS are as follows: Figure 3 Provide explanation.
[0155] like Figure 3As shown, assuming that the TA identified by TAC#1 is the RA of the UE, the list of network slices supported in the TA is {network slice #1, network slice #2, network slice #3, network slice #4, network slice #5, network slice #6} ("{}" represents a list), where the NS-AoS configured for network slice #2 is {Cell#1, Cell#3, Cell#4}. The UE initially communicates with the network in Cell#1. Since network slice #1 is congested or unavailable on the CN side, the AMF will send the corresponding relationship between network slice #1 and network slice #2 to the UE, that is, the original S-NSSAI is network slice #1, and the alternative S-NSSAI is network slice #2. Then, after the UE moves to Cell#2, it initiates a PDU session establishment request associated with network slice #1. At this time, the identifiers of network slice #1 and network slice #2 will be carried in the uplink NAS message. After receiving the two slice identifiers, the AMF will send the PDU session establishment request to the SMF. SMF will instruct to establish a PDU session associated with network slice #2, but since no resources are configured for network slice #2 in Cell #2, the PDU session associated with network slice #2 will fail to be established.
[0156] The present application provides a communication method to improve the possibility of successful PDU session establishment when the resident cell of the terminal device is located outside the service area of the network slice. For example, the communication method provided by the present application is intended to ensure that the PDU session requested by the UE is successfully established in the scenario where the UE moves to a cell outside the NS-AoS of the alternative S-NSSAI to initiate the PDU session of the original network slice and trigger the network slice replacement.
[0157] It should be understood that the communication method provided in the embodiment of the present application can be applied to a 5G system, for example, Figure 1 The communication system shown in .
[0158] It should also be understood that the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application, as long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application may be a device or a network element, or a functional module in a device or a network element that can call and execute a program.
[0159] Figure 4 This is a schematic flow chart of a communication method provided by the present application. It includes the following steps:
[0160] S410, the terminal device sends a first request message to the core network element, and correspondingly, the core network element receives the first request message from the terminal device.
[0161] The core network element involved in this embodiment may be the AMF mentioned above, and the name of the core network element is not limited in this embodiment. The network elements that can implement the functions of the core network element in this embodiment are within the protection scope of this application. For the convenience of description, the following description takes the core network element as AMF as an example.
[0162] It should be noted that when the terminal device sends the first request message to the core network element, the resident cell of the terminal device is the first cell, or the serving cell of the terminal device is the first cell. For example, after the terminal device located in the second cell moves to the first cell, it sends the above-mentioned first request message to the core network element.
[0163] Specifically, the first request message is used to request the establishment of a first PDU session associated with the first network slice. Exemplarily, the first request message may be an uplink NAS message including a PDU session establishment request message.
[0164] The first request message includes an identifier of a first network slice and an identifier of a second network slice, wherein the first network slice corresponds to the second network slice, the first network slice belongs to the allowed NSSAI of the terminal device, and the second network slice can be understood as a network slice that replaces the first network slice to provide services for the terminal device when the first network slice is congested or unavailable, and the service area of the second network slice does not include the first cell.
[0165] In this embodiment, the network slice is indicated by S-NSSAI, so the first request message includes the identifier of the first network slice and the identifier of the second network slice, which can be understood as the first request message includes the original S-NSSAI and the alternative S-NSSAI.
[0166] For ease of understanding, a scenario in which the terminal device sends a first request message to the AMF in this embodiment is described with reference to a specific example:
[0167] For example, the RA of the terminal device is the TA identified by TAC#1. Figure 3As shown in , the list of network slices supported in the TA is {network slice #1, network slice #2, network slice #3, network slice #4, network slice #5, network slice #6}. Among them, the NS-AoS configured for network slice #2 is {Cell #1, Cell #3, Cell #4}, that is, network slice #2 has no resources configured in Cell #2. The terminal device initially communicates with the network in the second cell (e.g., Cell #1). Since the first network slice (e.g., network slice #1) is congested or unavailable on the network side, the AMF can send the correspondence between the first network slice (e.g., network slice #1) and the second network slice (e.g., network slice #2) to the terminal device, that is, the original S-NSSAI is network slice #1, and the alternative S-NSSAI is network slice #2. The terminal device then moves to the first cell (e.g., Cell #2) and initiates a PDU session establishment request associated with network slice #1 (i.e., the first request message). At this time, the first request message will carry the identifiers of both network slice #1 and network slice #2 (i.e., the identifier of the first network slice and the identifier of the second network slice).
[0168] Further, in this embodiment, after the AMF receives the above-mentioned first request message (or the AMF responds to the received first request message), the AMF may determine based on the acquired configuration information that the first cell is located outside the service area of the second network slice, and there is at least one network slice with available resources in the first cell, then Figure 4 The method flow shown also includes:
[0169] S420, AMF determines based on the configuration information that the first cell is located outside the service area of the second network slice, and that there is at least one network slice with available resources in the first cell.
[0170] In this embodiment, the AMF determines, in response to the received first request message, that the first cell is located outside the service area of the second network slice and that there is at least one network slice with available resources in the first cell based on the configuration information. The configuration information is used to indicate the service area of the network slice configured within the registration area of the above-mentioned terminal device.
[0171] It can be understood that the above configuration information is used to indicate the service area of the network slice configured in the registration area of the terminal device: the configuration information is used to indicate the service area of the configured NSSAI in the registration area of the terminal device. Among them, the service area of the network slice can be understood as the service area corresponding to the network slice.
[0172] In addition, the network slice can be indicated by S-NSSAI, and the service area of the second network slice can be expressed as NS-AoS of the alternative S-NSSAI.
[0173] Exemplarily, AMF can obtain the above configuration information from OAM, or AMF can obtain the above configuration information based on historical communication data, or AMF can obtain the above configuration information from the access network device side. This embodiment does not impose any limitation on how AMF obtains the above configuration information.
[0174] For ease of understanding, a specific example is used to illustrate how the AMF determines, based on the configuration information, that the first cell is outside the service area of the second network slice and that there is at least one network slice with available resources in the first cell:
[0175] For example, the RA of the terminal device is the TA identified by TAC#1. Figure 3 As shown in , the list of network slices supported in the TA is {Network Slice #1, Network Slice #2, Network Slice #3, Network Slice #4, Network Slice #5, Network Slice #6}, and the configuration information is used to indicate that the NS-AoS configured for network slice #1 is {Cell #1, Cell #3}, the NS-AoS configured for network slice #2 is {Cell #1, Cell #3, Cell #4}, the NS-AoS configured for network slice #3 is {Cell #1, Cell #2, Cell #3}, network slice #4 is not configured with NS-AoS, and the NS-AoS configured for network slice #5 and network slice #6 is {Cell #1, Cell #2, Cell #4}. Among them, network slice #1 is understood as the first network slice in this embodiment, network slice #2 is understood as the second network slice in this embodiment, and Cell #2 is understood as the first cell in this embodiment. Therefore, AMF determines based on the configuration information that Cell #2 does not belong to the service area {Cell #1, Cell #3, Cell #4} of network slice #2, and AMF can determine based on the configuration information that there is at least one network slice with available resources in Cell #2, including: network slice #3, network slice #4, network slice #5 and network slice #6.
[0176] Specifically, in this embodiment, when the AMF determines that the first cell is located outside the service area of the second network slice, in order to avoid directly sending a PDU session establishment request associated with the second network slice to the access network device and causing subsequent PDU session establishment failure, the AMF can determine a third network slice from at least one network slice with available resources in the first cell, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the service provided by the first PDU session. Figure 4 The method flow shown also includes:
[0177] S430, AMF determines the third network slice.
[0178] Specifically, in this embodiment, the AMF may select a third network slice from the at least one network slice mentioned above. It should be noted that the third network slice determined by the AMF in this embodiment may be one or more network slices, that is, the network slices selected by the AMF from at least one network slice may be multiple. The resources configured by the third network slice in the first cell can be understood as the resources of the third network slice on the RAN side, or the resources configured by the third network slice on the RAN side.
[0179] In this embodiment, there is no limitation on the manner in which the AMF selects the third network slice from at least one network slice, including but not limited to the following selection manners:
[0180] 1) AMF randomly selects a third network slice from at least one network slice, and the third network slice is any one or more network slices among the above-mentioned at least one network slice.
[0181] For example, at least one network slice includes: network slice #3, network slice #4, network slice #5 and network slice #6, and the third network slice is any one or more network slices among network slice #3, network slice #4, network slice #5 and network slice #6.
[0182] 2) AMF selects a network slice with the same SST as the second network slice as the third network slice, and the SST of the third network slice is the same as the SST of the second network slice.
[0183] 3) AMF selects a network slice with the same SD as the second network slice as the third network slice, and the SD of the third network slice is the same as the SD of the second network slice.
[0184] For example, at least one network slice includes: network slice #3, network slice #4, network slice #5 and network slice #6, wherein the SST and / or SD of network slice #3 is the same as that of network slice #2, and the third network slice is network slice #3.
[0185] 4) AMF selects a network slice that has available resources in all cells within the registration area of the terminal device from at least one network slice as the third network slice, and the third network slice has available resources in all cells within the registration area of the terminal device.
[0186] For example, at least one network slice includes: network slice #3, network slice #4, network slice #5 and network slice #6, wherein network slice #4 has available resources in all cells within the registration area of the terminal device (e.g., network slice #4 is not configured with NS-AoS, or the NS-AoS configured for network slice #4 includes all cells within the registration area of the terminal device), and the third network slice is network slice #4.
[0187] 5) AMF selects a network slice within the first network slice group from at least one network slice as the third network slice, then the third network slice belongs to the first network slice group, and the first network slice group is associated with one or more network slices.
[0188] For example, at least one network slice includes: network slice #3, network slice #4, network slice #5 and network slice #6, wherein NSAG #1 exists in the UE RA and the slices associated with NSAG #1 are network slice #1 and network slice #5, and the third network slice is network slice #5.
[0189] 6) AMF selects the network slice with the most configured resources from at least one network slice as the third network slice, and the third network slice is the network slice with the most configured resources in the first cell.
[0190] For example, at least one network slice includes: network slice #3, network slice #4, network slice #5 and network slice #6, among which, based on the availability of slice resources reported by the access network device, it can be known that network slice #6 is the slice with the most available resources in the TA identified by TAC #1, and the third network slice is network slice #6.
[0191] It should be understood that the several methods of determining the third network slice shown in 1) to 6) above are only examples and do not constitute any limitation on the protection scope of this application. Other methods of AMF selecting the third network slice from at least one determined network slice are also within the protection scope of this application. For example, AMF selects the third network slice based on historical communication data; for example, the above 6 methods can also be used in combination to determine the third network slice. For example, the SST of network slice #3 is the same as that of network slice #2, and network slice #3 and network slice #4 are not configured with NS-AoS. If it can be determined that network slice #3 and network slice #4 are satisfied according to the above method 4), AMF can further determine that network slice #3 is the third network slice according to 2). I will not go into details here.
[0192] In addition, it should be noted that, in the process of determining at least one of the above-mentioned network slices, AMF can also determine the network slice that meets the rules based on one or more of the above-mentioned rules 1) to 6) as at least one network slice with available resources in the above-mentioned first message, which will not be repeated here.
[0193] Exemplarily, from the method of determining the third network slice shown in 6) above, it can be seen that AMF can refer to the auxiliary information reported by the access network device in the process of determining the third network slice. Figure 4 The method flow shown may also include:
[0194] S411, the access network device sends the first indication information to the AMF, and accordingly, the AMF receives the first indication information from the access network device.
[0195] The first indication information is used to indicate resource usage of network slices in at least one tracking area. Then AMF determines a third network slice from at least one network slice, including: AMF determines the third network slice from at least one network slice based on the first indication information.
[0196] In this embodiment, the first indication information provided by the access network device can also be understood as being used to indicate the resource usage of network slices in different cells.
[0197] For example, when the access network device is configured (for example, configured by OAM) with NS-AoS for one or more network slices, the access network device reports the availability of slice resources in each TA to AMF through NGAP signaling. The slices may be all slices in each TA, or slices in each TA that are not configured with NS-AOS (i.e., there are resources in all cells within the TA). The resource availability may be expressed as a percentage of available resources, or as an indication of whether the resources are congested. Optionally, the degree of congestion may be determined based on a preset threshold, which is not limited in this application.
[0198] In addition, in this embodiment, the AMF determines that the third network slice may be determined in response to trigger information of other devices. Figure 4 The method flow shown may also include:
[0199] S412, the access network device or the terminal device sends the second indication information to the AMF, and accordingly, the AMF receives the second indication information from the access network device or the terminal device.
[0200] The second indication information is used to instruct AMF to determine the third network slice. Then AMF determines the third network slice from at least one network slice, including: AMF determines the third network slice from at least one network slice in response to the second indication information.
[0201] From the above, it can be seen that the resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the service provided by the first PDU session. In this embodiment, the network slice associated with the second PDU session includes the following two possible implementation methods:
[0202] Implementation method 1: The network slice associated with the second PDU session is the second network slice.
[0203] In this implementation, Figure 4 The method flow shown also includes:
[0204] S431, AMF sends a second message to the access network device, and correspondingly, the access network device receives the second message from AMF.
[0205] The second message is used to request the establishment of a second PDU session. The second message includes third indication information, and the third indication information is used to indicate the establishment of the second PDU session using resources configured in the first cell using the third network slice.
[0206] Exemplarily, the AMF does not update the correspondence between the original S-NSSAI and the alternative S-NSSAI, and instructs the access network device to temporarily use the resources configured in the first cell of the third network slice.
[0207] For ease of understanding, possible forms of the second message are described with reference to specific examples:
[0208] For example, assuming that the second network slice is network slice #2, the second message is a PDU session resource establishment request, and the second message is used to instruct the access network device to establish a PDU session resource associated with network slice #2, and instruct the access network device to use the third network slice when preparing the access network device side resources for the PDU session. The resources configured in the access network device (ie, the third indication). Exemplarily, the AMF can carry the above information to the access network device through a PDU session resource establishment request (PDU session resource setup request), and an example of the relevant information element structure is shown in Table 1 below:
[0209] Table 1
[0210] PDU Session Resource Establishment Request >Session ID of the second PDU session >> Associate the second PDU session with network slice #2 >>Third instruction information
[0211] It should be understood that the information element structure shown in the table in this embodiment is only an example and does not constitute any limitation on the scope of protection of this application. For example, the "network slice #2 associated with the second PDU session" carried in the PDU session resource establishment request shown in Table 1 can be understood as carrying the S-NSSAI of network slice #2, or carrying the identifier of network slice #2. The network slices involved in the following tables (such as Table 2) can also be understood as the S-NSSAI or identifier of the network slice, and will not be repeated.
[0212] Implementation method two: The network slice associated with the second PDU session is the third network slice.
[0213] In the second implementation, Figure 4 The method flow shown also includes:
[0214] S432, AMF sends a first message to the access network device, and correspondingly, the access network device receives the first message from AMF.
[0215] The first message is used to request the establishment of a PDU session associated with the third network slice.
[0216] As a possible implementation method, AMF determines to establish a PDU session (CN side) associated with the second network slice, but instructs the access network device to establish a PDU session resource associated with the third network slice (optionally, if there are multiple third network slices, AMF can determine a third network slice as the network slice finally used, or, if there are multiple third network slices, AMF does not need to select a third network slice, but instructs the access network device to establish multiple third network slices respectively), and AMF saves the correspondence between the slices associated with the RAN side and the CN side of the PDU session. Exemplarily, AMF will carry the above information to the access network device through PDU Session Resource Setup Request, and the relevant information element structure example is shown in Table 2 below:
[0217] Table 2
[0218] PDU Session Resource Establishment Request >Session ID of the second PDU session >> Associate the third network slice of the second PDU session
[0219] As another possible implementation, AMF updates the alternative S-NSSAI corresponding to the original S-NSSAI. For example, the network slice corresponding to the first network slice is updated to the third network slice.
[0220] As described above, before receiving the first request message, the AMF determines that the first network slice corresponds to the second network slice when the resources of the first network slice in the core network are unavailable, and sends the fourth indication information indicating the correspondence between the first network slice and the second network slice to the terminal device. In this embodiment, when the AMF determines the third network slice, the AMF can update the network slice corresponding to the first network slice from the second network slice to the third network slice.
[0221] Exemplarily, when the AMF updates the alternative S-NSSAI corresponding to the original S-NSSAI, the AMF sends NAS signaling to the UE, where the NAS signaling is used to indicate that the first network slice corresponds to the third network slice.
[0222] Exemplarily, the first message is used to indicate the establishment of a PDU session associated with the third network slice. Exemplarily, the AMF will carry the above information to the access network device through a PDU session resource setup request. The relevant information element structure is shown in Table 2 above.
[0223] Further, after the access network device receives the above-mentioned first message or second message (or the access network device responds to the received first message or second message), a data radio bearer is established. Figure 4 The method flow shown also includes:
[0224] S440, the access network device establishes a data radio bearer.
[0225] Specifically, the access network device establishes a DRB associated with the third network slice to provide air interface data transmission for the UE.
[0226] As a possible implementation method, corresponding to the above-mentioned implementation method one, the access network device receives the second message, and determines to use the resources configured by the third network slice in the first cell to establish a PDU session associated with the second network slice based on the third indication information in the second message.
[0227] As another possible implementation method, corresponding to the above-mentioned implementation method 2, the access network device receives a first message, and in response to the first message, the access network device uses the resources configured by the third network slice in the first cell to establish a PDU session associated with the third network slice.
[0228] Optionally, if the access network device receives and saves the SMBRs of the first network slice (original S-NSSAI), the second network slice (alternative S-NSSAI) and the third network slice, the access network device may perform rate control on the PDU session based on the maximum, minimum or any SMBR among the three. For example, the access network device uses the SMBR of the third network slice for rate control, or performs rate control according to the SMBR corresponding to the network slice associated with the PDU session.
[0229] Optionally, if the access network device receives and saves one of the SMBRs of the first network slice (original S-NSSAI), the second network slice (alternative S-NSSAI), and the third network slice, the received SMBR is used to perform rate control on the PDU session.
[0230] Figure 4 In the communication method shown, the AMF responds to the received first request message, determines based on the configuration information that the first cell is located outside the service area of the second network slice, and determines a third network slice from at least one network slice when there is at least one network slice with available resources in the first cell. The resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session. In the case where the resident cell of the terminal device is outside the service area of the second network slice, by determining that there is a third network slice with available resources, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, the establishment of a PDU session associated with the network slice is achieved, thereby increasing the possibility of successful PDU session establishment and reducing service interruptions and delays.
[0231] The present application also provides a communication method, in which the terminal device determines the third network slice or the terminal device determines not to initiate a PDU session establishment request. Figure 5 This communication method is described in detail.
[0232] Figure 5 This is a schematic flow chart of a communication method provided by the present application. It includes the following steps:
[0233] S510, the terminal device receives the fourth indication information and configuration information from the AMF, and accordingly, the AMF sends the fourth indication information and configuration information to the terminal device.
[0234] The fourth indication information is used to indicate that the first network slice corresponds to the second network slice, and the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device.
[0235] It should be understood that this embodiment does not impose any limitation on the timing and manner in which the AMF sends the fourth indication information and configuration information to the terminal device. For example, the AMF may send the fourth indication information to the terminal device when it determines that the resources of the first network slice on the network side are congested or unavailable; for another example, the AMF may send the configuration information to the terminal device after obtaining the configuration information. In addition, the AMF may send the above-mentioned fourth indication information and configuration information to the terminal device through one message, or the AMF may send the above-mentioned fourth indication information and configuration information to the terminal device through different messages. I will not go into details here.
[0236] S520, the terminal device determines that the first cell is located outside the service area of the second network slice based on the fourth indication information and the configuration information.
[0237] Specifically, the first cell is a resident cell of the terminal device.
[0238] In this embodiment, a terminal device located in a resident cell (e.g., the terminal device moves to the first cell) can determine that the first cell is not within the service area of the second network slice based on the NS-AoS information (e.g., configuration information) configured for each slice (e.g., received from the AMF) and the correspondence between the first network slice and the second network slice (e.g., the fourth indication information) before initiating a PDU session request to establish an association with the first network slice (i.e., the original network slice).
[0239] Further, in this embodiment, when the terminal device determines that the first cell is not within the service area of the second network slice, further implementation of the terminal device includes but is not limited to the following possible implementations:
[0240] Implementation method three: The terminal device will initiate a PDU session for the first network slice within the service area of the second network slice. For example, the terminal device will initiate a PDU session for the first network slice only if it resides in a cell within the NS-AoS that is located in both the first network slice (original S-NSSAI) and the second network slice (alternative S-NSSAI).
[0241] Therefore, when it is determined that the first cell is not within the service area of the second network slice, the terminal device does not initiate a first PDU session request to establish the first network slice association in the first cell. Figure 5 The method flow shown may also include:
[0242] S521, the terminal device determines not to initiate a first PDU session request to establish a first network slice association within the first cell.
[0243] By not initiating the first PDU session request to establish the first network slice association within the first cell, subsequent PDU session establishment failures can be avoided and unnecessary resource overhead can be avoided.
[0244] Implementation mode 4: When the terminal device determines that the first PDU session request for establishing the first network slice association is initiated in the first cell, the terminal device determines that at least one network slice with available resources exists in the first cell based on the fourth indication information and the configuration information. In this implementation mode 4, Figure 5 The method flow shown may also include:
[0245] S522, determine to initiate a first PDU session request to establish a first network slice association, and determine at least one network slice with available resources in the first cell.
[0246] Specifically, in this embodiment, the method for the terminal device to determine at least one network slice in which available resources exist in the first cell can refer to the above Figure 4 The manner in which the AMF determines at least one network slice with available resources in the first cell in the communication method shown will not be repeated here.
[0247] Further, in this embodiment, when the terminal device determines that there is at least one network slice with available resources in the first cell and initiates a first PDU session request to establish the first network slice association, the subsequent execution mode of the terminal device includes the following possibilities:
[0248] Possibility 1: The terminal device determines the third network slice and notifies the network side (such as access network device or AMF) through the second indication information.
[0249] Specifically, in the case shown in Possible 1, Figure 5 The method flow shown also includes:
[0250] S531, the terminal device determines the third network slice.
[0251] Specifically, the method for the terminal device to determine the third network slice in this embodiment can refer to the above Figure 4 The way in which AMF determines the third network slice in the communication method shown will not be repeated here.
[0252] In this possible implementation, after the terminal device determines the third network slice, it can indicate the third network slice to the network side through the following possible indication methods (such as the following indication method 1 and indication method 2), Figure 5 The method flow shown also includes:
[0253] S532, the terminal device sends a second indication message to the AMF or access network device.
[0254] The second indication information is used to indicate a third network slice in at least one network slice. The resources configured by the third network slice in the first cell are used to establish a second PDU session. For example, the second indication information carries an identifier of the third network slice, and the second indication information can be used to indicate the use of resources on the RAN side of the third network slice to provide services for the second PDU session.
[0255] Possibility two: The terminal device instructs the network side to determine the third network slice.
[0256] Specifically, in the case shown in Possible 2, Figure 5 The method flow shown also includes: the above-mentioned S532, the difference is that in the case shown in the second possibility, the second indication information is used to instruct the network side (such as an access network device or an AMF) to determine the third network slice, wherein the resources configured in the first cell of the third network slice are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session.
[0257] Exemplarily, in a case where the second indication information is used to indicate the determination of the third network slice, after receiving the second indication information, the network side determines the third network slice in response to the second indication information. Figure 5 The method flow shown also includes:
[0258] S533, AMF or access network equipment determines the third network slice.
[0259] As a possible implementation method, AMF determines the third network slice.
[0260] In this implementation, the way in which AMF determines the third network slice can also refer to Figure 4 In the communication method shown, AMF determines the third network slice mode after receiving the first request message.
[0261] Optionally, in this embodiment, after receiving the second indication information, the AMF can directly determine the third network slice in response to the second indication information, without determining that the first cell is located outside the service area of the second network slice. For example, after receiving the second indication information, the AMF determines one or more network slices with available resources in the first cell as the third network slice based on the configuration information.
[0262] Optionally, in this embodiment, after receiving the second indication information, the AMF determines the manner and Figure 4 In the communication method shown, after the AMF receives the first request message, the method of determining the third network slice is exactly the same. It will also judge based on the configuration information that the first cell is located outside the service area of the second network slice, and there is at least one network slice with available resources in the first cell.
[0263] As another possible implementation, the access network device determines the third network slice.
[0264] In this implementation, the way in which the access network device determines the third network slice can also refer to Figure 4 In the communication method shown, AMF determines the third network slice mode after receiving the first request message.
[0265] Optionally, in this embodiment, after receiving the second indication information, the access network device can directly determine the third network slice in response to the second indication information, without determining that the first cell is located outside the service area of the second network slice. For example, after receiving the second indication information, the access network device determines one or more network slices with available resources in the first cell as the third network slice based on the configuration information.
[0266] Optionally, in this embodiment, after the access network device receives the second indication information, the method and Figure 4 In the communication method shown, after the AMF receives the first request message, the third network slice is determined in the same way. It will also be determined based on the configuration information that the first cell is outside the service area of the second network slice, and there is at least one network slice with available resources in the first cell.
[0267] It should be understood that in the manner in which AMF determines the third network slice, the subsequent process after AMF determines the third network slice can refer to Figure 4 In the communication method shown, the process after AMF determines the third network slice is not repeated here. For example, the access network device is instructed to establish a second PDU session through a first message or a second message.
[0268] In this embodiment, the subsequent process after the access network device determines the third network slice can refer to the following Figure 6 The method in which the access network device determines the third network slice is shown and will not be described in detail here.
[0269] Indication method 1: The terminal device first indicates the third network slice to the AMF through the second indication information (for example, when the terminal device has determined the third network slice); or indicates to the AMF through the second indication information that the third network slice has been determined (for example, when the terminal device has not determined the third network slice). The AMF then indicates the third network slice to the access network device.
[0270] Exemplarily, the above-mentioned second indication information is carried in the PDU session establishment request. For example, when the terminal device initiates a PDU session request associated with the first network slice, the identifiers of the first network slice and the second network slice are carried in the PDU session establishment request. In addition, under the indication method, the PDU session establishment request also carries the second indication information, and the second indication information is used to indicate that the resources for establishing the second PDU session on the access network device side can use the resources configured on the access network device side of the third network slice, or is used to instruct the AMF to determine the third network slice for the access network device side for use by the PDU session associated with the second network slice. The NAS message element structure is shown in Table 3 below:
[0271] Table 3
[0272] >PDU session establishment request >The identifier of the first network slice and the identifier of the second network slice >Second instruction information
[0273] Optionally, in the case shown in the first indication method, if the terminal device expects AMF to update the network slice corresponding to the first network slice from the second network slice to the third network slice, the second indication information can also be used to indicate that the network slice corresponding to the first network slice is updated from the second network slice to the third network slice.
[0274] For example, when the terminal device initiates a PDU session request associated with the first network slice, the identifiers of the first network slice and the second network slice are carried in the PDU session establishment request. In addition, in the indication method, the PDU session establishment request also carries second indication information, which is used to indicate the third network slice or indicate the determination of the third network slice, and is also used to instruct the AMF to update the network slice corresponding to the first network slice from the second network slice to the third network slice. Or,
[0275] In the case where the second indication information instructs AMF to determine the third network slice, AMF will automatically update the network slice corresponding to the first network slice from the second network slice to the third network slice after determining the third network slice, without the need for the second indication information to additionally instruct to update the network slice corresponding to the first network slice from the second network slice to the third network slice.
[0276] Further, after receiving the second indication information, AMF can directly read and obtain the above-mentioned third network slice from the second indication information, that is, the second indication information indicates the third network slice, or, after receiving the second indication information, AMF determines the third network slice in response to the second indication information.
[0277] Specifically, the process after AMF determines the third network slice refers to the above Figure 4 The communication method shown will not be repeated here.
[0278] Indication method two: the terminal device indicates the third network slice to the access network device through the second indication information (for example, when the terminal device has determined the third network slice); or indicates to the access network device to determine the third network slice through the second indication information (for example, when the terminal device has not determined the third network slice).
[0279] Exemplarily, the above-mentioned second indication information is carried in an RRC message, the RRC message includes an uplink NAS message, and the uplink NAS message includes a PDU session establishment request message. For example, when the terminal device initiates a PDU session request associated with the first network slice, the identifiers of the first network slice and the second network slice are carried in the PDU session establishment request, and the RRC message carrying the PDU session establishment request indicates that the access network device side can use the resources configured on the access network device side of the third network slice when establishing the access network device side resources for the PDU session, or instructs the access network device to determine the third network slice for use by the PDU session associated with the second network slice through the RRC message.
[0280] Exemplarily, the RRC message may be an uplink message transmission (UL information transfer), and the second indication information in the RRC may be associated with the ID of the PDU session. The information element structure is shown in Table 4 below:
[0281] Table 4
[0282] UL information transfer >NAS message (PDU session establishment request to associate the first network slice with the second network slice) >Second instruction information
[0283] Under the second indication mode, the access network device transmits the PDU session establishment request (such as NAS message) to AMF through NGAP signaling.
[0284] Exemplarily, the access network device may send a PDU session establishment request to AMF via an uplink NAS transport (UL NAS Transport). After receiving the PDU session establishment request, AMF may instruct the access network device to establish a PDU session resource associated with the second network slice based on the correspondence between the first network slice and the second network slice. After receiving the instruction from AMF, the access network device uses the resources configured on the access network device side of the third network slice to establish the PDU session based on the second instruction information previously received from the terminal device side.
[0285] S540: The access network device establishes a data radio bearer.
[0286] refer to Figure 4 In the communication method shown, the description of step S440 is not repeated here.
[0287] Figure 5 In the communication method shown, when the terminal device determines that a request for establishing a first PDU session associated with a first network slice is initiated in the first cell, the terminal device can determine based on the received information (such as the fourth indication information and the configuration information): the first cell is located outside the service area of the second network slice corresponding to the first network slice, and there is at least one network slice with available resources in the first cell. Further, the terminal device indicates a third network slice in at least one network slice through the second indication information, or instructs the network side (such as an access network device or a core network element) to determine a third network slice, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session. In the case where the resident cell of the terminal device is outside the service area of the second network slice, by determining that there is a third network slice with available resources, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, the establishment of a PDU session associated with the network slice is achieved, thereby increasing the possibility of successful PDU session establishment and reducing service interruption and delay.
[0288] Alternatively, the terminal device determines not to initiate PDU session establishment, thereby avoiding subsequent PDU session establishment failures and unnecessary resource overhead.
[0289] The present application also provides a communication method, in which the access network device determines the third network slice mentioned above. Figure 6 This communication method is described in detail.
[0290] Figure 6 This is a schematic flow chart of a communication method provided by the present application. It includes the following steps:
[0291] S610, the terminal device sends a first request message to the AMF, and accordingly, the AMF receives the first request message from the terminal device.
[0292] Refer to the above Figure 4 The description of step S410 is not repeated here.
[0293] S620, AMF sends a second request message to the access network device, and correspondingly, the access network device receives the second request message from AMF.
[0294] The second request message is used to request the establishment of a PDU session associated with the second network slice in the first cell. Exemplarily, the AMF instructs the access network device to establish a PDU session associated with the second network slice through a PDU Session Resource Setup Request.
[0295] In this embodiment, after the access network device receives the second request message (or the access network device responds to the received second request message), the access network device may determine based on the acquired configuration information that the first cell is outside the service area of the second network slice, and there is at least one network slice with available resources in the first cell, then Figure 6 The method flow shown also includes:
[0296] S630, the access network device determines based on the configuration information that the first cell is located outside the service area of the second network slice, and that there is at least one network slice with available resources in the first cell.
[0297] Specifically, the way in which the access network device in this embodiment determines at least one network slice in which available resources exist in the first cell can refer to the above Figure 4 The manner in which the AMF determines at least one network slice with available resources in the first cell in the communication method shown will not be repeated here.
[0298] Optionally, when the access network device is configured (for example, configured by OAM) with NS-AoS for one or more network slices, the access network device reports the availability of slice resources in each TA to the AMF through NGAP signaling. For example, the access network device sends a first indication message to the AMF, where the first indication message is used to indicate the resource usage of network slices in at least one tracking area, or the first indication message is used to indicate the resource usage of network slices in different cells.
[0299] Exemplarily, in this embodiment, the access network device determines that the first cell is located outside the service area of the second network slice, and that there is at least one network slice with available resources in the first cell, and the subsequent process performed includes the following two possible implementation methods:
[0300] As a possible implementation method, the access network device determines a third network slice from at least one network slice, and the resources configured in the first cell of the third network slice are used to establish a PDU session associated with the second network slice.
[0301] In this implementation, Figure 6 The method flow shown also includes:
[0302] S631, the access network device determines the third network slice.
[0303] The access network device determines a third network slice from at least one network slice, and the resources configured in the first cell by the third network slice are used to establish a PDU session associated with the second network slice, and the PDU session associated with the second network slice is used to provide the terminal device with the services provided by the first PDU session.
[0304] For example, based on configuration information (such as NS-AoS information configured for each slice), the access network device knows that the first cell where the terminal device currently resides is outside the NS-AoS of the second network slice (alternative S-NSSAI), and there are other slices (such as the third network slice) in the first cell with available resources. The access network device can use the access network device-side resources of the third network slice to establish a PDU session associated with the second network slice.
[0305] As another possible implementation method, the access network device instructs the AMF to determine the third network slice through the fifth indication information.
[0306] In this implementation, Figure 6 The method flow shown also includes:
[0307] S632, the access network device sends the fifth indication information to AMF.
[0308] The fifth indication information is used to indicate the third network slice or to instruct the AMF to determine the third network slice.
[0309] For example, based on the configuration information (e.g., NS-AoS information configured for each slice), the access network device knows that the first cell where the terminal device currently resides is outside the NS-AoS of the second network slice (alternative S-NSSAI), and there are other slices in the first cell (e.g., network slices other than the first network slice and the second network slice) with available resources. The access network device instructs the AMF to determine the third network slice through the fifth indication information (e.g., included in the NGAP message, the fifth indication information can be associated with the ID of the PDU session), and the subsequent behavior of the AMF refers to Figure 4 .
[0310] Optionally, in this implementation, the fifth indication information may also be used to instruct the AMF to update the network slice corresponding to the first network slice from the second network slice to the third network slice. After the AMF updates the network slice corresponding to the first network slice from the second network slice to the third network slice according to the instruction, the access network device may be instructed to modify the slice associated with the current PDU session to the third network slice. Or,
[0311] In the case where the fifth indication information instructs AMF to determine the third network slice, AMF will automatically update the network slice corresponding to the first network slice from the second network slice to the third network slice after determining the third network slice, without the need for the fifth indication information to additionally instruct to update the network slice corresponding to the first network slice from the second network slice to the third network slice.
[0312] Exemplarily, the NGAP message may be a PDU session resourcesetup response or an UplinkNAS transport, and the cell structure is shown in Table 5 or Table 6 below:
[0313] Table 5
[0314] PDU Session Resource Establishment Response >Session ID of the second PDU session >>Fifth instruction information
[0315] Table 6
[0316] Uplink NAS transmission >AMF UE NGAP ID >RAN UE NGAP ID >NAS PDU >Fifth instruction information
[0317] S640: The access network device establishes a data radio bearer.
[0318] refer to Figure 4 In the communication method shown, the description of step S440 is not repeated here.
[0319] Figure 6 In the communication method shown, after receiving the second request message, the access network device determines based on the configuration information that: the first cell is located outside the service area of the second network slice corresponding to the first network slice, and there is at least one network slice with available resources in the first cell. Therefore, in the process of establishing the DRB, the access network device can establish a DRB associated with the third network slice in at least one network slice instead of the DRB associated with the second network slice, use the resources of the third network slice with available resources, establish a PDU session associated with the network slice, and realize the establishment of the PDU session associated with the network slice, thereby increasing the possibility of successful establishment of the PDU session and reducing service interruption and delay.
[0320] It should be understood that the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0321] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.
[0322] It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for exemplary description (such as AMF, UE, gNB, etc.), and it should be understood that the specific form of the device is not limited in the embodiments of the present application. For example, devices that can achieve the same function in the future are applicable to the embodiments of the present application.
[0323] It can be understood that in the above-mentioned method embodiments, the methods and operations implemented by the device (such as AMF, UE, gNB) can also be implemented by components of the device (such as chips or circuits).
[0324] Above, combined Figures 4 to 6 The communication method provided by the embodiment of the present application is described in detail. The above communication method is mainly introduced from the perspective of interaction between various protocol layers of the terminal device. It can be understood that in order to realize the above functions, the terminal device includes a hardware structure and / or software module corresponding to each function.
[0325] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0326] The following combination Figures 7 to 9 The communication device provided by the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, the content not described in detail can be referred to the method embodiment above, and some content will not be repeated for the sake of brevity.
[0327] The embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.
[0328] Figure 7 1 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application. The device 10 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can implement corresponding communication functions, and the processing module 12 is used to perform data processing, or in other words, the transceiver module 11 is used to perform operations related to receiving and sending, and the processing module 12 is used to perform other operations besides receiving and sending. The transceiver module 11 can also be called a communication interface or a communication unit.
[0329] Optionally, the device 10 may further include a storage module 13, which may be used to store instructions and / or data. The processing module 12 may read the instructions and / or data in the storage module so that the device implements the actions of the devices in the aforementioned method embodiments.
[0330] In one design, the device 10 may correspond to the AMF in the above method embodiment, or be a component (such as a chip) of the AMF.
[0331] The device 10 can implement the steps or processes corresponding to the AMF execution in the above method embodiment, wherein the transceiver module 11 can be used to perform the AMF transceiver related operations in the above method embodiment, and the processing module 12 can be used to perform the AMF processing related operations in the above method embodiment.
[0332] In a possible implementation, the transceiver module 11 is used to receive a first request message from a terminal device, wherein the first request message is used to request the establishment of a first protocol data unit (PDU) session associated with a first network slice, and the first request message includes an identifier of the first network slice and an identifier of a second network slice. The processing module 12 is used to determine, in response to the first request message, that the first cell is located outside the service area of the second network slice based on configuration information, and to determine at least one network slice in the first cell where there are available resources, wherein the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device, and the first cell is the resident cell of the terminal device. The processing module 12 is used to determine a third network slice from the at least one network slice, wherein the resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session.
[0333] In another possible implementation, the transceiver module 11 is used to receive second indication information, where the second indication information is used to indicate a third network slice, or the second indication information is used to indicate the determination of the third network slice, where the third network slice is a network slice with available resources in the first cell. The processing module 12 is used to determine the third network slice in response to the second indication information, where the resources configured by the third network slice in the first cell are used to establish a second protocol data unit PDU session, where the second PDU session is used to provide the terminal device with the services provided by the first PDU session, wherein the first cell is located outside the service area of the second network slice, the first PDU session is a PDU session associated with the first network slice requested to be established by the terminal device, the first network slice corresponds to the second network slice, and the first cell is a resident cell of the terminal device.
[0334] Wherein, when the device 10 is used to perform Figure 4 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S411, S412, S410, S431 and S432; the processing module 12 can be used to execute the processing steps in the method, such as steps S420 and S430.
[0335] When the device 10 is used to perform Figure 5 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S510 and S532; the processing module 12 can be used to execute the processing steps in the method, such as step S533.
[0336] When the device 10 is used to perform Figure 6When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S610 and S620; the processing module 12 can be used to execute the processing steps in the method.
[0337] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.
[0338] In another design, the apparatus 10 may correspond to the terminal device in the above method embodiment, or be a component (such as a chip) of the terminal device.
[0339] The device 10 can implement the steps or processes executed by the terminal device in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver related operations of the terminal device in the above method embodiment, and the processing module 12 can be used to execute the processing related operations of the terminal device in the above method embodiment.
[0340] In a possible implementation, the transceiver module 11 is used to receive fourth indication information and configuration information, wherein the fourth indication information is used to indicate that the first network slice corresponds to the second network slice, and the configuration information is used to indicate the service area of the network slice configured in the registration area of the terminal device. The processing module 12 is used to determine that when the first cell initiates a request for establishing a first protocol data unit PDU session associated with the first network slice, based on the fourth indication information and the configuration information, the first cell is located outside the service area of the second network slice, and at least one network slice with available resources in the first cell is determined, and the first cell is the resident cell of the terminal device. The transceiver module 11 is used to send second indication information, wherein the second indication information is used to indicate a third network slice in the at least one network slice, or the second indication information is used to indicate the determination of the third network slice, wherein the resources configured in the first cell for the third network slice are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session.
[0341] In a possible implementation, the transceiver module 11 is used to receive fourth indication information and configuration information, wherein the fourth indication information is used to indicate that the first network slice corresponds to the second network slice, and the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device. The processing module 12 is used to determine that the first cell is located outside the service area of the second network slice based on the third indication information and the configuration information, and not initiate a first protocol data unit PDU session request to establish the first network slice association in the first cell.
[0342] Wherein, when the device 10 is used to perform Figure 4 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S410 and S412; the processing module 12 can be used to execute the processing steps in the method.
[0343] When the device 10 is used to perform Figure 5 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S510 and S532; the processing module 12 can be used to execute the processing steps in the method, such as steps S520, S521, S522 and S531.
[0344] When the device 10 is used to perform Figure 6 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as step S610; the processing module 12 can be used to execute the processing steps in the method.
[0345] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.
[0346] In yet another design, the apparatus 10 may correspond to the access network device in the above method embodiment, or a component (such as a chip) of the access network device.
[0347] The device 10 can implement the steps or processes executed by the access network device in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver-related operations of the access network device in the above method embodiment, and the processing module 12 can be used to execute the processing-related operations of the access network device in the above method embodiment.
[0348] In a possible implementation, the transceiver module 11 is used to receive a second request message, wherein the second request message is used to request to establish a protocol data unit (PDU) session associated with a second network slice in the first cell. The processing module 12 is used to determine that the first cell is located outside the service area of the second network slice based on configuration information, and to determine at least one network slice in the first cell where there are available resources, wherein the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device. The processing module 12 is used to establish a data radio bearer (DRB) associated with a third network slice in the at least one network slice, wherein the DRB is used to provide air interface data transmission for the terminal device; wherein the first cell is a resident cell of the terminal device, the first cell is located outside the service area of the second network slice, and the resources configured by the third network slice in the first cell are used to establish a PDU session associated with the second network slice.
[0349] Wherein, when the device 10 is used to perform Figure 4When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S412, S411, S431 and S432; the processing module 12 can be used to execute the processing steps in the method, such as step S440.
[0350] When the device 10 is used to perform Figure 5 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method; the processing module 12 can be used to execute the processing steps in the method, such as step S540.
[0351] When the device 10 is used to perform Figure 6 When the method is performed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S620 and S632; the processing module 12 can be used to execute the processing steps in the method, such as steps S630, S631 and S640.
[0352] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.
[0353] It should also be understood that the device 10 here is embodied in the form of a functional module. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art may understand that the device 10 may be specifically a mobile management network element in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the mobile management network element in the above-mentioned method embodiments; or, the device 10 may be specifically a terminal device in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the terminal device in the above-mentioned method embodiments. To avoid repetition, it will not be repeated here.
[0354] The device 10 of each of the above schemes has the function of implementing the corresponding steps performed by the devices (such as terminal devices, access network devices and core network network elements) in the above methods. This function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as processing modules, can be replaced by processors to respectively perform the transceiver operations and related processing operations in each method embodiment.
[0355] In addition, the transceiver module 11 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing module may be a processing circuit.
[0356] Figure 8 2 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. The device 20 includes a processor 21, and the processor 21 is used to execute a computer program or instruction stored in a memory 22, or read data / signaling stored in the memory 22 to execute the method in each method embodiment above. Optionally, there are one or more processors 21.
[0357] Alternatively, if Figure 7 As shown, the device 20 also includes a memory 22, which is used to store computer programs or instructions and / or data. The memory 22 can be integrated with the processor 21, or can also be separately set. Optionally, the memory 22 is one or more.
[0358] Alternatively, if Figure 7 As shown, the device 20 further includes a transceiver 23, and the transceiver 23 is used for receiving and / or sending signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.
[0359] As a solution, the device 20 is used to implement the operations performed by the AMF in the above method embodiments.
[0360] As another solution, the device 20 is used to implement the operations performed by the terminal device in the above various method embodiments.
[0361] As another solution, the device 20 is used to implement the operations performed by the access network device in the above method embodiments.
[0362] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
[0363] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0364] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.
[0365] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0366] Fig. 9 Schematic diagram of a chip system 30 provided in an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.
[0367] Among them, the logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 30 can implement the methods and functions of each embodiment of the present application. The input / output interface 32 can be an input / output circuit in the chip system 30, outputting information processed by the chip system 30, or inputting data or signaling information to be processed into the chip system 30 for processing.
[0368] As a solution, the chip system 30 is used to implement the operations performed by the AMF, terminal device, or access network device in the above method embodiments.
[0369] For example, the logic circuit 31 is used to implement the processing-related operations performed by the AMF, terminal device, or access network device in the above method embodiments; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the AMF, terminal device, or access network device in the above method embodiments.
[0370] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods performed by the AMF, terminal device, or access network device in the above-mentioned method embodiments.
[0371] For example, when the computer program is executed by a computer, the computer can implement the methods performed by the AMF, terminal device, or access network device in each embodiment of the above method.
[0372] An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by the AMF, terminal device, or access network device in the above-mentioned method embodiments.
[0373] The embodiment of the present application further provides a communication system, including the aforementioned AMF and access network equipment. Optionally, the communication system also includes the aforementioned terminal equipment.
[0374] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.
[0375] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0376] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0377] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0378] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0379] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0380] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0381] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0382] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A communication method, characterized in that: include: Receive a first request message from a terminal device, where the first request message is used to request establishment of a first protocol data unit (PDU) session associated with a first network slice, and the first request message includes an identifier of the first network slice and an identifier of a second network slice; In response to the first request message, determining based on configuration information that the first cell is located outside the service area of the second network slice, and determining that at least one network slice having available resources exists in the first cell, the configuration information being used to indicate the service area of the network slice configured within the registration area of the terminal device, the first cell being a resident cell of the terminal device; A third network slice is determined from the at least one network slice, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session.
2. The method according to claim 1, characterized in that The method further comprises: Receive first indication information, where the first indication information is used to indicate resource usage of a network slice within at least one tracking area; The determining a third network slice from the at least one network slice comprises: The third network slice is determined from the at least one network slice based on the first indication information.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: receiving second indication information, where the second indication information is used to indicate determination of the third network slice; The determining a third network slice from the at least one network slice comprises: The third network slice is determined from the at least one network slice in response to the second indication information.
4. The method according to any one of claims 1 to 3, characterized in that The first network slice corresponds to the second network slice, In the case where a third network slice is determined from the at least one network slice, the method further includes: The network slice corresponding to the first network slice is updated from the second network slice to the third network slice.
5. The method according to any one of claims 1 to 4, characterized in that The second PDU session is a PDU session associated with the third network slice, and the method further includes: Send a first message, where the first message is used to request establishment of a PDU session associated with the third network slice.
6. The method according to any one of claims 1 to 3, characterized in that The second PDU session is a PDU session associated with the second network slice, and the method further includes: A second message is sent, where the second message is used to request establishment of the second PDU session, and the second message includes third indication information, where the third indication information is used to indicate establishment of the second PDU session using resources configured in the first cell using the third network slice.
7. The method according to any one of claims 1 to 6, characterized in that The third network slice satisfies at least one of the following conditions: The slice service type SST and / or slice distinction SD of the third network slice are the same as the SST and / or SD of the second network slice; or, The third network slice has available resources in all cells within the registration area of the terminal device; or, The third network slice belongs to a first network slice group, and the first network slice group is associated with one or more network slices; or The third network slice is the network slice with the most resources configured in the first cell.
8. A communication method, characterized in that: include: Receive a second message, where the second message is used to request establishment of a protocol data unit (PDU) session associated with a second network slice, where the second message includes third indication information, where the third indication information is used to indicate that the PDU session associated with the second network slice is established using resources configured by a third network slice in the first cell, where the third network slice is determined by the core network element based on configuration information when the first cell is outside the service area of the second network slice and there is at least one network slice with available resources in the first cell, from the at least one network slice; Establishing a data radio bearer DRB associated with the third network slice, wherein the DRB is used to provide air interface data transmission for the terminal device; The configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device, and the first cell is the resident cell of the terminal device.
9. The method according to claim 8, characterized in that The method further comprises: The data transmission rate is controlled based on any one of the slice maximum bit rate SMBR of the first network slice, the SMBR of the second network slice, or the SMBR of the third network slice, wherein the first network slice and the second network slice correspond to each other.
10. The method according to claim 8 or 9, characterized in that: The method further comprises: Send first indication information, where the first indication information is used to indicate resource usage of a network slice within at least one tracking area.
11. A communication system, comprising a core network element and an access network device, characterized in that: The core network element is used to receive a first request message from a terminal device, where the first request message is used to request establishment of a first protocol data unit (PDU) session associated with a first network slice, and the first request message includes an identifier of the first network slice and an identifier of a second network slice; The core network element is further used to, in response to the first request message, determine, based on configuration information, that the first cell is located outside the service area of the second network slice, and determine that at least one network slice having available resources exists in the first cell, wherein the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device, and the first cell is a resident cell of the terminal device; The core network element is further used to determine a third network slice from the at least one network slice, and the resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with a service provided by the first PDU session; The access network device is used to receive a second message from the core network network element, where the second message is used to request to establish the second PDU session, and the second message includes third indication information, where the third indication information is used to indicate to use the resources configured by the third network slice in the first cell to establish the second PDU session; The access network device is also used to establish a data radio bearer DRB associated with the third network slice, and the DRB is used to provide air interface data transmission for the terminal device.
12. A communication method, characterized in that: include: Receive fourth indication information and configuration information, where the fourth indication information is used to indicate that the first network slice corresponds to the second network slice, and the configuration information is used to indicate a service area of the network slice configured in a registration area of the terminal device; The terminal device determines that, when the first cell initiates a first protocol data unit PDU session request to establish the first network slice association, the first cell is located outside the service area of the second network slice based on the fourth indication information and the configuration information, and at least one network slice with available resources is determined in the first cell, and the first cell is a resident cell of the terminal device; sending second indication information, where the second indication information is used to indicate a third network slice in the at least one network slice, or the second indication information is used to indicate determination of the third network slice, The resources configured by the third network slice in the first cell are used to establish a second PDU session, and the second PDU session is used to provide the terminal device with the services provided by the first PDU session.
13. The method according to claim 12, characterized in that In a case where the second indication information is used to indicate a third network slice in the at least one network slice, the method further includes: The third network slice is determined from the at least one network slice.
14. The method according to claim 12 or 13, characterized in that The second indication information is also used to indicate that the network slice corresponding to the first network slice is updated from the second network slice to the third network slice.
15. The method according to any one of claims 12 to 14, characterized in that The third network slice satisfies at least one of the following conditions: The slice service type SST and / or slice distinction SD of the third network slice are the same as the SST and / or SD of the second network slice; or, The third network slice has available resources in all cells within the registration area of the terminal device; or, The third network slice belongs to a first network slice group, and the first network slice group is associated with one or more network slices; or The third network slice is the network slice with the most resources configured in the first cell.
16. A communication method, characterized in that: include: receiving second indication information, where the second indication information is used to indicate a third network slice, or the second indication information is used to indicate determination of the third network slice, where the third network slice is a network slice for which available resources exist in the first cell; In response to the second indication information, the third network slice is determined, and the resources configured by the third network slice in the first cell are used to establish a second protocol data unit PDU session, and the second PDU session is used to provide the terminal device with the service provided by the first PDU session, The first cell is located outside the service area of the second network slice, the first PDU session is a PDU session associated with the first network slice requested to be established by the terminal device, the first network slice corresponds to the second network slice, and the first cell is a resident cell of the terminal device.
17. The method according to claim 16, characterized in that In a case where the second indication information is used to indicate determination of the third network slice, the method further includes: Determine based on configuration information that the first cell is outside the service area of the second network slice, and determine that at least one network slice having available resources exists in the first cell, wherein the configuration information is used to indicate the service area of the network slice configured within the registration area of the terminal device; The third network slice is determined from the at least one network slice.
18. The method according to claim 17, characterized in that The method further comprises: The network slice corresponding to the first network slice is updated from the second network slice to the third network slice.
19. The method according to any one of claims 16 to 18, characterized in that The second PDU session is a PDU session associated with the second network slice, and the method further includes: A second message is sent, where the second message is used to request establishment of the second PDU session, and the second message includes third indication information, where the third indication information is used to indicate establishment of the second PDU session using resources configured in the first cell using the third network slice.
20. The method according to any one of claims 16 to 18, characterized in that The second indication information is also used to indicate that the network slice corresponding to the first network slice is updated from the second network slice to the third network slice, and the second PDU session is a PDU session associated with the third network slice. The method also includes: Send a first message, where the first message is used to request establishment of a PDU session associated with the third network slice.
21. The method according to claim 16 or 17, characterized in that The method further comprises: A data radio bearer DRB associated with the third network slice is established, and the DRB is used to provide air interface data transmission for the terminal device.
22. A communication device, characterized in that: The communication device comprises a processor and a memory, wherein the processor and the memory are coupled, and the memory is used to store a computer program. When the processor runs the computer program, the communication device executes the method according to any one of claims 1 to 21.
23. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a communication device, the communication device is caused to execute the method according to any one of claims 1 to 21.
24. A computer program product, characterized in that The method comprises computer instructions, which, when executed on a communication device, cause the communication device to execute the method according to any one of claims 1 to 21.
25. A chip, characterized in that: The chip includes a processor and a communication interface. The processor reads and runs instructions through the communication interface. When the chip is installed in a communication device, the communication device executes the method as described in any one of claims 1-21.
26. A communication system, characterized in that: The communication system comprises a terminal device and a network device, wherein the terminal device is used to execute the method according to any one of claims 1-21.
Citation Information
Cited By
Communication method and communication apparatus
EP4791111A1
Communication method and communication apparatus
WO2025086936A1