CN109792657B

CN109792657B - Wireless communication method and apparatus

Info

Publication number: CN109792657B
Application number: CN201780057715.2A
Authority: CN
Inventors: 刘建华
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2017-10-26
Filing date: 2017-10-26
Publication date: 2020-08-18
Anticipated expiration: 2037-10-26
Also published as: WO2019080070A1; CN109792657A; CN111901842B; CN111901842A

Abstract

The embodiment of the application provides a wireless communication method and equipment, which can realize the specific application of network slicing. The method comprises the following steps: the method comprises the steps that network equipment receives a first message sent by terminal equipment, wherein the first message is used for requesting network slicing service or indicating the network slicing capability of the terminal equipment; the network equipment sends a first feedback message aiming at the first message to the terminal equipment.

Description

Wireless communication method and apparatus

Technical Field

The present application relates to the field of communications, and more particularly, to a wireless communication method and apparatus.

Background

In New Radio (NR) systems, network slicing may be supported. The network slice is to divide a hardware infrastructure into a plurality of virtual end-to-end networks, and each network slice is logically isolated to adapt to different characteristic requirements of various types of services.

At present, no specific application of network slicing in NR systems is given.

Therefore, how to apply network slices is an urgent problem to be solved.

Disclosure of Invention

The embodiment of the application provides a wireless communication method and equipment, which can realize the specific application of network slicing.

In a first aspect, a wireless communication method is provided, including:

the method comprises the steps that network equipment receives a first message sent by terminal equipment, wherein the first message is used for requesting network slicing service or indicating the network slicing capability of the terminal equipment;

the network equipment sends a first feedback message aiming at the first message to the terminal equipment.

Therefore, in this embodiment of the present application, a network device receives a first message sent by a terminal device for requesting a network slicing service or for indicating a network slicing capability of the terminal device, and sends a first feedback message for the first message to the terminal device, so that flexible application of a network slice to a specific scene is realized through interaction between the network device and the terminal device.

With reference to the first aspect, in a possible implementation manner of the first aspect, the sending, by a network device, a first feedback message for a first message to a terminal device includes:

and according to the network slicing capability of the terminal equipment, the network equipment sends a first feedback message to the terminal equipment.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the sending, by the network device, the first feedback message to the terminal device according to the network slicing capability of the terminal device includes:

and the network equipment sends a first feedback message to the terminal equipment according to whether the network slicing capability of the terminal equipment belongs to the network slicing capability supported by the network.

With reference to the first aspect or any one of the foregoing possible implementations, in another possible implementation of the first aspect, the first feedback message is used to indicate:

whether the network slicing capability of the terminal equipment belongs to the network slicing capability supported by the network or not; or

The network slicing capability of the terminal equipment is supported by the network; or the like, or, alternatively,

the network slicing capability of the terminal device does not belong to the network slicing capability supported by the network.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, when all or part of the network slice capabilities in the network slice capabilities of the terminal device belong to the network slice capabilities supported by the network device, the first feedback message carries configuration information for performing network slice configuration on the terminal device.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the method further includes:

the network equipment acquires the network slicing capability of the terminal equipment from a first message, wherein the first message is used for indicating the network slicing capability of the terminal equipment; or the like, or, alternatively,

the network device obtains the network slicing capability of the terminal device from a subscription server of the terminal device, wherein the first message is used for requesting a network slicing service.

With reference to the first aspect or any one of the foregoing possible implementations, in another possible implementation of the first aspect, the network slicing capability of the terminal device is used to indicate at least one of:

the number of network slices supported by the terminal device;

identification information of a network slice supported by the terminal device;

the type of traffic of the network slice supported by the terminal device.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the requesting a network slicing service by a first message, and sending, by a network device, a feedback message for the first message to a terminal device, includes:

and the network equipment sends a first feedback message according to whether the network can meet the network slicing service requested by the terminal equipment.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the sending, by the network device, the first feedback message according to the network slicing service that the network device can satisfy the request of the terminal device includes:

when the network can meet the network slicing service requested by the terminal equipment, the network equipment sends a first feedback message, wherein the first feedback message carries configuration information for carrying out network slicing configuration on the terminal equipment.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the sending, by the network device, the first feedback message according to whether the network can satisfy the network slicing service requested by the terminal device includes:

and when the network can not meet the network slicing service requested by the terminal equipment, sending a first feedback message, wherein the first feedback message is used for rejecting the network slicing service request.

With reference to the first aspect or any one of the foregoing possible implementations, in another possible implementation of the first aspect, the first message is used to request a network slice service, and the first message further indicates a network slice requesting to join.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the sending, by the network device, a first feedback message for the first message to the terminal device includes:

the network equipment determines whether the network slice requested to be added by the terminal equipment is the network slice signed by the terminal equipment;

and sending a first feedback message according to whether the network slice requested to be added by the terminal equipment is the network slice signed by the terminal equipment.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the sending a first feedback message according to whether a network slice requested to be added by the terminal device is a network slice subscribed by the terminal device includes:

when all or part of the network slices requested by the terminal equipment belong to the network slices signed by the terminal equipment, sending a first feedback message, wherein the first feedback message carries configuration information for configuring the network slices to the terminal equipment, and the configured network slices belong to the network slices signed by the terminal equipment.

and when all or part of the network slices requested by the terminal equipment do not belong to the network slices signed by the terminal equipment, sending a first feedback message, wherein the first feedback message is used for refusing to carry out network slice service on the terminal equipment.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the first feedback message carries a cause value for rejecting a network slicing service to the terminal device, where the cause value is a network slice that all or part of network slices requested by the terminal device do not belong to a subscription of the terminal device.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the determining, by the network device, whether the network slice requested to be joined by the terminal device is a network slice subscribed by the terminal device includes:

the network equipment sends a second message to a signing server of the terminal equipment, and the second message indicates the network slice which the terminal equipment requests to join;

receiving a second feedback message sent by the signing server aiming at the second message, wherein the second feedback message is used for indicating whether the network slice requested to be added by the terminal equipment is the network slice signed by the terminal equipment;

and determining whether the network slice requested to be added by the terminal equipment is the network slice signed by the terminal equipment or not according to the second feedback message.

the network equipment sends a third message to a signing server of the terminal equipment, wherein the third message is used for requesting the signing information of the terminal equipment;

receiving a third feedback message sent by the subscription server aiming at the third message, wherein the third feedback message carries subscription information of the terminal equipment;

and determining whether the network slice requested to be added by the terminal equipment is the network slice signed by the terminal equipment or not according to the signing information of the terminal equipment.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the first message is a registration message.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the first feedback message is a registration rejection message, and the reason value for rejecting registration carried in the first feedback message is that a network slicing service requested by the terminal device is not supported, or a network slicing capability of the terminal device does not belong to a network slicing capability supported by the network device.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the first feedback message carries indication information indicating that the terminal device is rejected for performing the network slicing service.

With reference to the first aspect or any one of the foregoing possible implementations, in another possible implementation of the first aspect, the first feedback message further carries a cause value of the rejection.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the first feedback message carries configuration information for performing network slice configuration on the network device.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the configuration information includes:

type information of the configured network slice;

configured identification information of network handover;

information of the number of configured network handovers.

With reference to the first aspect or any one of the foregoing possible implementations, in another possible implementation of the first aspect, the service type includes at least one of:

the mobile broadband eMBB is enhanced, URLLC is communicated with low time delay and high reliability, and mIOT is a large-scale internet of things.

With reference to the first aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the first aspect, the network device is a core network device.

In a second aspect, a wireless communication method is provided, including:

the method comprises the steps that terminal equipment sends a first message to network equipment, wherein the first message is used for requesting network slicing service or indicating the network slicing capability of the terminal equipment;

the terminal equipment receives a first feedback message sent by the network equipment aiming at the first message.

With reference to the second aspect, in a possible implementation manner of the second aspect, the first message is used to request a network slice service, and the first message further indicates a network slice requesting to join.

With reference to the second aspect or any one of the foregoing possible implementations, in another possible implementation of the second aspect, the network slicing capability of the terminal device is used to indicate at least one of:

the number of network slices supported by the terminal device;

identification information of a network slice supported by the terminal device;

the type of traffic of the network slice supported by the terminal device.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the second aspect, the first feedback message carries indication information indicating that the network slicing service is rejected to the terminal device.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the second aspect, the first feedback message carries a cause value for rejecting network slicing service for the terminal device.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the second aspect, the method further includes:

the terminal device sends a first message to other network devices having a different public land mobile network, PLMN, or radio access technology, RAT, than the network device.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the second aspect, the first feedback message carries configuration information for performing network slice configuration on the terminal device.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the second aspect, the configuration information includes:

information of the service type of the configured network slice;

configured identification information of network handover;

information of the number of configured network handovers.

With reference to the second aspect or any one of the foregoing possible implementations, in another possible implementation of the second aspect, the service type includes at least one of:

With reference to the second aspect or any one of the foregoing possible implementations, in another possible implementation of the second aspect, the first feedback message is used to indicate:

when all or part of the network slicing capability of the terminal device does not belong to the network slicing capability supported by the network, the terminal device sends a first message to other network devices which have different PLMN or RAT with the network device.

With reference to the second aspect or any one of the foregoing possible implementations, in another possible implementation of the second aspect, the first message is a registration message.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the second aspect, the first feedback message is a registration rejection message, and the reason value for rejecting registration carried in the first feedback message is that a network slicing service requested by the terminal device is not supported, or a network slicing capability of the terminal device does not belong to a network slicing capability supported by the network device.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the second aspect, the sending, by the terminal device, the first message to the network device includes:

the first message is sent to the network device based on a public land mobile network, PLMN, radio access technology, RAT, or area in which the network device is located.

With reference to the second aspect or any one of the foregoing possible implementation manners, in another possible implementation manner of the second aspect, the network device is a core network device.

In a third aspect, a network device is provided, configured to perform the method in the first aspect or any possible implementation manner of the first aspect. In particular, the network device comprises functional modules for performing the method of the first aspect or any possible implementation manner of the first aspect.

In a fourth aspect, there is provided a terminal device configured to perform the method of the second aspect or any possible implementation manner of the second aspect. In particular, the terminal device comprises functional modules for performing the method of the second aspect or any possible implementation manner of the second aspect.

In a fifth aspect, a network device is provided that includes a processor, a memory, and a transceiver. The processor, the memory and the transceiver communicate with each other via an internal connection path to transmit control and/or data signals, so that the network device performs the method of the first aspect or any possible implementation manner of the first aspect.

In a sixth aspect, a terminal device is provided that includes a processor, a memory, and a transceiver. The processor, the memory and the transceiver communicate with each other via the internal connection path to transmit control and/or data signals, so that the terminal device performs the method of the second aspect or any possible implementation manner of the second aspect.

In a seventh aspect, a computer-readable medium is provided for storing a computer program comprising instructions for performing any one of the above methods or any possible implementation.

In an eighth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform any one of the methods described above or any possible implementation thereof.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic flow chart of a wireless communication method according to an embodiment of the application.

Fig. 2 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 3 is a schematic block diagram of a terminal device according to an embodiment of the present application.

FIG. 4 is a schematic block diagram of a system chip according to an embodiment of the present application.

Fig. 5 is a schematic block diagram of a communication device according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a global system for Mobile communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, UMTS) system, a Frequency Division Duplex (FDD) system, a Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for microwave Access (WiMAX) communication system, or a 5G system (NR 5G system).

In a communication system, a mobile network needs to serve various types and demands of devices. Common application scenarios may include mobile broadband, large-scale internet of things, mission-critical internet of things. These scenarios may employ different types of networks, with varying requirements in terms of mobility, charging, security, policy control, latency, reliability, etc.

For example, large-scale internet of things services connect fixed sensors to measure temperature, humidity, rainfall, etc. The features of handover, location update, etc. of those primary serving handsets in the mobile network are not required. In addition, the mission-critical internet of things services such as automatic driving and remote control robots require end-to-end delay of several milliseconds, which is very different from the mobile broadband service.

This does not mean that a dedicated network needs to be built for each service, since multiple logical networks can be split across a single physical network by network slicing techniques to save cost.

The network slice refers to a plurality of virtual end-to-end networks which can be obtained by dividing hardware infrastructure, wherein each network slice is logically isolated from a terminal to access network equipment, to a transmission network and then to a core network, and can be adapted to different characteristic requirements of various types of services.

For each network slice, dedicated resources such as virtual servers, network bandwidth, quality of service, etc. can be fully guaranteed. Because the slices are isolated from each other, an error or failure of one slice may not affect the communication of other slices.

To implement Network slicing, Network Function Virtualization (NFV) may be employed. Basically, the main idea of NFV is to deploy network function software to virtual machines on servers, rather than separately to their dedicated network devices. In this way, the access network may act as an edge cloud while the core functionality acts as a core cloud. The connection between Virtual Machines (VMs) located in the edge and core clouds may be configured. Slices may then be created for each service (i.e., telephony service, large-scale internet of things service, mission critical internet of things service, etc.).

Network slices are introduced above, but the network slices mentioned in the embodiments of the present application are not limited to the above descriptions.

The wireless communication method, the network device, the terminal and the device provided below provide a specific application of the network slice.

Fig. 1 is a schematic flow chart diagram of a wireless communication method 100 according to an embodiment of the present application. The method 100 includes at least some of the following.

In 110, the terminal device sends a first message to the network device, the first message being for requesting a network slicing service or for indicating a network slicing capability of the terminal device.

Optionally, the terminal device mentioned in the embodiments of the present application may be mobile or fixed. Alternatively, a terminal device can refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, 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 an evolved PLMN.

Optionally, the network device mentioned in this embodiment may be a core network device.

Optionally, when the first message is used for requesting a network slice service, the first message may also indicate a network slice requesting to join, but may also not carry the network slice requesting to join.

Optionally, when the first message is used to indicate the network slicing capability of the terminal device, it may also be used to simultaneously request a network slicing service.

Optionally, the network slicing capability of the terminal device is used to indicate at least one of:

the number of network slices supported by the terminal device;

identification information of the network slice supported by the terminal device;

the service types of the network slices supported by the terminal equipment.

Optionally, when the network slice capability of the terminal device in the first message is used to indicate the number of network slices supported by the terminal, it means that the number information may be carried in the first message, and also the identification information of the specifically supported network slices may be carried, so that the supported number may be indirectly indicated.

Optionally, when the network slice capability of the terminal device in the first message is used to indicate the identification information of the network slice supported by the terminal, it means that the identification information may be carried in the first message.

Optionally, when the network slice capability of the terminal device in the first message is used to indicate the service type of the network slice supported by the terminal, it means that the service type information may be carried in the first message.

Optionally, the service types mentioned in the embodiments of the present application may be enhanced mobile broadband (eMBB), Low Latency and high reliability Communication (URLLC), and mass internet of things (mlot).

Optionally, in this embodiment of the application, the terminal device may send the first message to the Network device based on a Public Land Mobile Network (PLMN), a Radio Access Technology (RAT), or a region in which the Network device is located. The area mentioned in the embodiments of the present application may be a service area or a registration area.

Specifically, the network slice capabilities supported by the terminal device may be different in different PLMNs, RATs or areas, and at this time, the first message needs to be sent for the PLMN, RAT or area corresponding to the current network device.

Or, the terminal device may determine a PLMN, a RAT, or an area according to network slice capabilities supported by each PLMN, RAT, or area, and send the first message to a network device corresponding to the determined PLMN, RAT, or area.

Specifically, the terminal device may determine, according to the network slicing capabilities supported by the respective PLMNs, RATs or areas and the network slicing capabilities supported by the terminal device, a PLMN, a RAT or an area that matches the network slicing capabilities supported by the terminal device, and send the first message to the matching PLMN, RAT or area.

Optionally, the first message mentioned in this embodiment may be a registration message.

Specifically, the terminal device may send the first message in any registration process, that is, report the network slicing capability supported by itself to the network device, or request a network slicing service. Alternatively, the terminal device may change the network slicing capability information or change the requested network slicing service at any registration procedure.

At 120, the network device receives the first message sent by the terminal device.

In 130, the network device sends a first feedback message for the first message to the terminal device.

Specifically, after receiving the first message, the network device may feed back the first message according to the current actual situation. For a clearer understanding, several feedback modes will be described below. It should be understood that the various feedback methods described below are not independent, and that features of the various feedback methods may be combined without contradiction.

In one implementation, the network device sends the first feedback message to the terminal device according to the network slicing capability of the terminal device.

Specifically, the network device may send the first feedback message to the terminal device according to whether the network slicing capability of the terminal device belongs to network slicing capabilities supported by a network.

Specifically, the network device needs to acquire the network slicing capability supported by the terminal device, then determines whether the network slicing capability supported by the terminal device belongs to the network slicing capability supported by the network in combination with the network slicing capability supported by the network, and then feeds back a determination result.

Optionally, the first feedback message may indicate: whether the network slicing capability of the terminal device belongs to the network slicing capabilities supported by the network.

Specifically, the network device may feed back to the terminal device whether the network slicing capability of the terminal device is supported by the network. For example, assuming that the first message carries the number of network slices supported by the terminal device, it may be fed back whether the number of network slices is supported by the network. For example, assuming that the first message carries identification information of network slices supported by the terminal device, it may be fed back whether the network slices of the respective identification information are supported by the network. For example, assuming that the first message carries the service types of the network slices supported by the terminal device, it may be fed back whether the network slices of the respective service types are supported by the network.

Optionally, the first feedback message may indicate: the network slicing capability of the terminal device belongs to the network slicing capability supported by the network.

In particular, the network device may feed back to the terminal device the supported network slicing capabilities of the terminal device. For example, assuming that the first message carries the number of network slices supported by the terminal device, the number of network slices actually capable of being supported by the network may be fed back, and the number of network slices actually capable of being supported by the network may be smaller than the number of network slices supported by the terminal device. For example, assuming that the first message carries identification information of network slices supported by the terminal device, the identification information of the network device slices supported by the network may be fed back. For example, assuming that the first message carries the service type of the network slice supported by the terminal device, the service type of the network slice supported by the network may be fed back.

Optionally, the first feedback message may indicate: the network slicing capability of the terminal device does not belong to the network slicing capabilities supported by the network.

Specifically, the network device may feed back to the terminal device network slice capabilities that are not supported in the network slice capabilities of the terminal device. For example, assuming that the first message carries the number of network slices supported by the terminal device, the number of network slices not actually supported by the network may be fed back, which may be equal to the number of network slices supported by the terminal device minus the number of network slices actually capable of being supported by the network. For example, assuming that the first message carries identification information of network slices supported by the terminal device, identification information of network device slices not supported by the network may be fed back. For example, assuming that the first message carries the traffic type of the network slice supported by the terminal device, the traffic type of the network slice not supported by the network may be fed back.

Optionally, when all or part of the network slice capabilities in the network slice capabilities of the terminal device belong to the network slice capabilities supported by the network device, the first feedback message carries configuration information for performing network slice configuration on the terminal device.

Specifically, when all network slice capabilities in the network slice capabilities of the terminal device belong to the network slice capabilities supported by the network device, the terminal device may be configured for network slice. Or, when a part of the network slicing capabilities in the network slicing capabilities of the terminal device belong to the network slicing capabilities supported by the network device, the network slicing configuration may be performed on the terminal device.

Wherein the configuration information may indicate at least one of a number of configured network slices, identification information and a traffic type.

Alternatively, the configured network slice may be simultaneously compliant with the capabilities of the terminal device and also with the capabilities of the network device.

For example, the number of configured network slices is less than or equal to the number of network slices supported by the terminal device, and is also less than or equal to the number of network slices supported by the terminal device by the network.

For example, the identification information of the configured network slice is identification information of a network slice supported by the terminal device, and is also identification information of a network slice supported by the network device.

For example, the service type of the configured network slice is the service type of the network slice supported by the terminal device, and is also the service type of the network slice supported by the network device.

Optionally, when all or part of the network slicing capabilities of the terminal device do not belong to the network slicing capabilities supported by the network device, if the first message is used for requesting a network slicing service, the first feedback message is used for rejecting the network slicing service request.

Optionally, the cause value may be carried when the first feedback message is used to reject the network slicing service request.

Optionally, when the first message is a registration message, the first feedback message may be a registration rejection message, and the reason value for rejecting registration carried in the first feedback message is that the network slicing service requested by the terminal device is not supported, or the network slicing capability of the terminal device does not belong to the network slicing capability supported by the network device.

Optionally, the network device obtains the network slicing capability of the terminal device from the first message, where the first message is used to indicate the network slicing capability of the terminal device.

Optionally, the network device obtains the network slicing capability of the terminal device from a subscription server of the terminal device, where the first message is used to request a network slicing service.

In one implementation, the network device sends the first feedback message according to whether the network can satisfy the network slicing service requested by the terminal device.

Optionally, the first message is for requesting a network slice service, and optionally further indicates a network slice requesting to join.

Or, the first message is used to request a network slicing service, and optionally, the first message also carries network slicing capabilities supported by the terminal device.

Optionally, when the network can meet the network slice service requested by the terminal device, the network device sends the first feedback message, where the first feedback message carries configuration information for performing network slice configuration on the terminal device.

The configured network slice may be a network slice which the terminal device requests to join; the network slice may not be the network slice requested to join by the terminal device, and specifically may be the network slice configured according to the network slice capability supported by the terminal device (the network device may obtain the capability from the subscription server).

Optionally, when the network cannot meet the network slicing service requested by the terminal device, the first feedback message is sent, and the first feedback message is used for rejecting the network slicing service request.

Specifically, assuming that the network device does not support the number of network slices requested by the terminal device, the network slice having specific identification information or the traffic type of the requested network slice, the network slice service request may be rejected. Or, if the number, the identification information, and/or the service type of the network slice supported by the network device does not correspond to the number, the identification information, and/or the service type of the network slice supported by the terminal device, the network slice service request may be rejected.

In one implementation, the network device determines whether the network slice requested to be joined by the terminal device is a network slice signed by the terminal device; and sending the first feedback message according to whether the network slice requested to be added by the terminal equipment is the network slice signed by the terminal equipment.

Optionally, when all or part of the network slices requested by the terminal device belong to the network slice subscribed by the terminal device, the first feedback message is sent, where the first feedback message carries configuration information for performing network slice configuration on the terminal device, and the configured network slice belongs to the network slice subscribed by the terminal device.

Optionally, when all or part of the network slices requested by the terminal device do not belong to the network slice subscribed by the terminal device, the first feedback message is sent, and the first feedback message is used to refuse to perform the network slice service on the terminal device.

Optionally, the first feedback message carries a cause value for refusing to perform the network slicing service on the terminal device, where the cause value is that all or part of the network slices requested by the terminal device do not belong to the network slices subscribed by the terminal device.

Optionally, the network device sends a second message to a subscription server of the terminal device, where the second message indicates a network slice requested to be added by the terminal device; receiving a second feedback message sent by the subscription server for the second message, wherein the second feedback message is used for indicating whether the network slice requested to be added by the terminal device is the network slice subscribed by the terminal device; and determining whether the network slice requested to be added by the terminal equipment is the network slice signed by the terminal equipment or not according to the second feedback message.

Optionally, the network device sends a third message to a subscription server of the terminal device, where the third message is used to request subscription information of the terminal device; receiving a third feedback message sent by the subscription server for the third message, wherein the third feedback message carries subscription information of the terminal device; and determining whether the network slice requested to be added by the terminal equipment is the network slice signed by the terminal equipment or not according to the signing information of the terminal equipment.

In 140, the terminal device receives the first feedback message sent by the network device for the first message.

Optionally, when the terminal device learns, through feedback of the network device, that all or part of the network slice capabilities of the terminal device do not belong to the network slice capabilities supported by the network, the terminal device sends the first message to another network device having a different PLMN or RAT from the network device.

Optionally, when the first feedback message indicates that network slicing service for the terminal is rejected, the terminal device sends the first message to other network devices having different PLMNs or RATs from the network device.

Fig. 2 is a schematic block diagram of a network device 200 according to an embodiment of the present application. As shown in fig. 2, the network device 200 includes a receiving unit 210 and a feedback unit 220; wherein the receiving unit 210 is configured to: receiving a first message sent by a terminal device, wherein the first message is used for requesting a network slicing service or indicating the network slicing capability of the terminal device; the feedback unit 220 is configured to: and sending a first feedback message aiming at the first message to the terminal equipment.

It should be understood that the network device 200 may correspond to a network device in the method embodiment, and corresponding operations implemented by the network device in the method embodiment may be implemented, which are not described herein again for brevity.

Fig. 3 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application. As shown in fig. 3, the terminal device 300 includes a transmitting unit 310 and a receiving unit 320; wherein the sending unit 310 is configured to: sending a first message to a network device, wherein the first message is used for requesting a network slicing service or indicating the network slicing capability of the terminal device; the receiving unit 320 is configured to: and receiving a first feedback message sent by the network equipment for the first message.

It should be understood that the terminal device 300 may correspond to a terminal device in the method embodiment, and corresponding operations implemented by the terminal device in the method embodiment may be implemented, which are not described herein again for brevity.

Fig. 4 is a schematic structural diagram of a system chip 600 according to an embodiment of the present application. The system chip 600 of fig. 4 includes an input interface 601, an output interface 602, the processor 603, and a memory 604, which may be connected via an internal communication connection, and the processor 603 is configured to execute codes in the memory 604.

Optionally, when the code is executed, the processor 603 implements a method performed by a network device in the method embodiment. For brevity, no further description is provided herein.

Optionally, when the code is executed, the processor 603 implements the method performed by the terminal device in the method embodiment. For brevity, no further description is provided herein.

Fig. 5 is a schematic block diagram of a communication device 700 according to an embodiment of the present application. As shown in fig. 5, the communication device 700 includes a processor 710 and a memory 720. The memory 720 can store program codes, and the processor 710 can execute the program codes stored in the memory 720.

Alternatively, as shown in fig. 7, the communication device 700 may include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate externally.

Optionally, the processor 710 may call the program code stored in the memory 720 to perform corresponding operations of the network device in the method embodiment, which is not described herein for brevity.

Optionally, the processor 710 may call the program code stored in the memory 720 to perform corresponding operations of the terminal device in the method embodiment, which is not described herein for brevity.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, comprising:

the method comprises the steps that network equipment receives a first message sent by terminal equipment, wherein the first message is used for indicating the network slicing capability of the terminal equipment;

the network equipment sends a first feedback message aiming at the first message to the terminal equipment according to whether the network slicing capability of the terminal equipment belongs to the network slicing capability supported by the network;

wherein the first message is a registration message, and the first feedback message is used to indicate:

whether the network slicing capability of the terminal equipment belongs to the network slicing capability supported by the network; or, the network slicing capability of the terminal device is the network slicing capability supported by the network; or the network slicing capability of the terminal device does not belong to the network slicing capability supported by the network.

2. The method of claim 1, wherein the first feedback message carries configuration information for network slice configuration for the terminal device when all or a part of the network slice capabilities of the terminal device belong to network slice capabilities supported by the network device.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and the network equipment acquires the network slicing capability of the terminal equipment from the first message.

4. The method according to claim 1 or 2, wherein the network slicing capability of the terminal device is used to indicate at least one of:

the number of network slices supported by the terminal device;

and the service types of the network slices supported by the terminal equipment.

5. The method of claim 1, wherein the first feedback message is a registration rejection message, and wherein the first feedback message carries a registration rejection cause value, and wherein the cause value comprises that the network slice capability of the terminal device does not belong to network slice capabilities supported by the network device.

6. The method of claim 1 or 2, wherein the first feedback message carries configuration information for network slice configuration of the network device.

7. The method of claim 6, wherein the configuration information comprises:

service type information of the configured network slice;

configured identification information of network handover;

information of the number of configured network handovers.

8. The method of claim 7, wherein the traffic type comprises at least one of:

9. The method of claim 1, 2 or 5, wherein the network device is a core network device.

10. A method of wireless communication, comprising:

the method comprises the steps that a terminal device sends a first message to a network device, wherein the first message is used for indicating the network slicing capability of the terminal device;

the terminal equipment receives a first feedback message sent by the network equipment aiming at the first message according to whether the network slicing capability of the terminal equipment belongs to the network slicing capability supported by the network or not;

11. The method of claim 10, wherein the network slicing capability of the terminal device is used to indicate at least one of:

the number of network slices supported by the terminal device;

12. The method according to claim 10 or 11, wherein the first feedback message carries configuration information for network slice configuration of the terminal device.

13. The method of claim 12, wherein the configuration information comprises:

information of the service type of the configured network slice;

configured identification information of network handover;

information of the number of configured network handovers.

14. The method of claim 13, wherein the traffic type comprises at least one of:

15. The method of claim 10, further comprising:

when all or part of the network slice capability of the terminal device does not belong to the network slice capability supported by the network, the terminal device sends the first message to other network devices having different PLMNs or RATs from the network device.

16. The method of claim 10, wherein the first feedback message is a registration reject message, and wherein the first feedback message carries a registration reject cause value, and wherein the cause value comprises that the network slice capability of the terminal device does not belong to the network slice capabilities supported by the network device.

17. The method according to claim 10 or 11, wherein the terminal device sends a first message to a network device, comprising:

sending the first message to the network device based on a Public Land Mobile Network (PLMN), a Radio Access Technology (RAT) or an area in which the network device is located.

18. The method according to claim 10, 11 or 15, wherein the network device is a core network device.

19. A network device, comprising a receiving unit and a feedback unit; wherein

The receiving unit is used for: receiving a first message sent by a terminal device, wherein the first message is used for indicating the network slicing capability of the terminal device;

the feedback unit is used for: sending a first feedback message aiming at the first message to the terminal equipment according to whether the network slicing capability of the terminal equipment belongs to the network slicing capability supported by the network;

20. The device according to claim 19, wherein the first feedback message carries configuration information for network slice configuration for the terminal device when all or a part of the network slice capabilities of the terminal device belong to the network slice capabilities supported by the network device.

21. The apparatus of claim 19 or 20, wherein the feedback unit is further configured to:

and acquiring the network slicing capability of the terminal equipment from the first message.

22. The device according to any of claims 19 or 20, wherein the network slicing capability of the terminal device is used to indicate at least one of:

the number of network slices supported by the terminal device;

23. The device of claim 19, wherein the first feedback message is a registration reject message, and wherein the first feedback message carries a registration reject cause value, and wherein the cause value comprises that the network slice capability of the terminal device does not belong to network slice capabilities supported by the network device.

24. The device of claim 19 or 20, wherein the first feedback message carries configuration information for network slice configuration of the network device.

25. The apparatus of claim 24, wherein the configuration information comprises:

service type information of the configured network slice;

configured identification information of network handover;

information of the number of configured network handovers.

26. The apparatus of claim 25, wherein the traffic type comprises at least one of:

27. The device of claim 19, 20 or 23, wherein the network device is a core network device.

28. A terminal device is characterized by comprising a transmitting unit and a receiving unit; wherein the content of the first and second substances,

the sending unit is used for: sending a first message to a network device, wherein the first message is used for indicating the network slicing capability of the terminal device;

the receiving unit is used for: receiving a first feedback message sent by the network equipment aiming at the first message according to whether the network slicing capability of the terminal equipment belongs to the network slicing capability supported by the network;

29. The device of claim 28, wherein the network slice capability of the terminal device is configured to indicate at least one of:

the number of network slices supported by the terminal device;

30. The device according to claim 28 or 29, wherein the first feedback message carries configuration information for network slice configuration for the terminal device.

31. The apparatus of claim 30, wherein the configuration information comprises:

information of the service type of the configured network slice;

configured identification information of network handover;

information of the number of configured network handovers.

32. The apparatus of claim 31, wherein the traffic type comprises at least one of:

33. The apparatus of claim 28, wherein the sending unit is further configured to:

when all or part of the network slice capability of the terminal device does not belong to the network slice capability supported by the network, the first message is sent to other network devices which have different PLMN or RAT with the network device.

34. The device of claim 28, wherein the first feedback message is a registration reject message, and wherein the first feedback message carries a registration reject cause value, and wherein the cause value comprises that the network slice capability of the terminal device does not belong to network slice capabilities supported by the network device.

35. The apparatus of claim 28, 29 or 33, wherein the sending unit is further configured to:

36. The device of claim 28, 29 or 33, wherein the network device is a core network device.