WO2023185295A1 - 通信方法及终端设备、核心网设备 - Google Patents
通信方法及终端设备、核心网设备 Download PDFInfo
- Publication number
- WO2023185295A1 WO2023185295A1 PCT/CN2023/076228 CN2023076228W WO2023185295A1 WO 2023185295 A1 WO2023185295 A1 WO 2023185295A1 CN 2023076228 W CN2023076228 W CN 2023076228W WO 2023185295 A1 WO2023185295 A1 WO 2023185295A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- slice
- indication information
- terminal device
- slices
- rejected
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 191
- 238000004891 communication Methods 0.000 title claims abstract description 143
- 230000015654 memory Effects 0.000 claims description 44
- 238000013507 mapping Methods 0.000 claims description 38
- 238000004590 computer program Methods 0.000 claims description 20
- 230000008569 process Effects 0.000 description 54
- 230000006870 function Effects 0.000 description 36
- 238000007726 management method Methods 0.000 description 22
- 238000010586 diagram Methods 0.000 description 16
- 238000012545 processing Methods 0.000 description 16
- 238000013523 data management Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 9
- 230000001960 triggered effect Effects 0.000 description 8
- 230000000977 initiatory effect Effects 0.000 description 7
- 230000001360 synchronised effect Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 101150096310 SIB1 gene Proteins 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
Definitions
- the present application relates to the field of communication technology, and in particular, to a communication method, terminal equipment, and core network equipment.
- the fifth generation (5G) communication system introduces the concept of network slicing.
- Network slicing technology can divide a physical network into multiple virtual networks.
- a virtual network is treated as a "network slice", and each network slice is independent of each other.
- Different sessions in an end device may require network slices corresponding to each session to provide services.
- the terminal device carries the requested network slice when requesting to register to the network, and after successfully registering to the network, obtains the allowed network slice and registration area from the network side, and any tracking area terminal within the registration area All devices can access the allowed network slice and use the services provided by the allowed network slice.
- the end device even if it is in a tracking area that supports the denied network slice end devices are not allowed to use the denied network slice. Therefore, it greatly limits the number or types of network slices that terminal devices can use within the current network coverage, and also limits the types of PDU sessions that terminal devices can establish. It cannot meet the needs of terminal devices for communication through the use of network slices. .
- Embodiments of the present application provide a wireless communication method, terminal equipment, and core network equipment, in order to better meet the needs of terminal equipment for communication by using network slicing.
- a communication method including:
- the terminal device sends a first registration request message to the core network device in the first tracking area TA;
- the terminal device receives a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is used to indicate The second TA supports the first slice, the second TA belongs to the first RA, and the first slice belongs to the information of the rejected slice;
- the terminal device When the terminal device moves from the first TA to the second TA, the terminal device sends a second registration request message to the core network device according to the first indication information.
- the second registration request The message includes the first slice.
- the terminal device When the terminal device moves from the first TA to the second TA, and the terminal device responds to current business requirements (for example, the usage requirements of a certain APP) determine that it needs to access the first slice to establish a PDU session, and according to the instructions of the first indication information, the terminal device can learn that the second TA currently located supports the first slice. Since the first slice The slice is a slice that is refused to be used in the current RA (first RA). Therefore, the terminal device triggers the registration process by itself and sends the registration request message (i.e., the second registration request message) to the AMF again.
- the second registration request message carries The requested slice includes the first slice, and after obtaining approval from the AMF, the terminal device can access the first slice for communication.
- the registration acceptance message also carries a first indication message.
- the terminal device can know in which TA a specific rejected slice is available, for example, according to the first indication message
- An indication information allows the terminal to know that the rejected first slice is actually available in the second TA. In this way, after the terminal device moves to the second TA, if it still wants to use the first slice for network communication (such as establishing PDU session), you can initiate a registration request again to request access to the first slice.
- the above settings can expand the number or types of network slices that the terminal device can use within the current wireless network coverage, and also increase the types of PDU sessions that the terminal device can establish, satisfying the needs of the terminal device through use to a greater extent. Network slicing is required for communication, thereby improving user experience.
- the first indication information includes an identifier of the second TA and an identifier of the first slice.
- the first indication information includes support information of multiple TAs for the rejected slice, and the support information is used to indicate that the rejected slices among the multiple TAs
- Each TA supports at least one of the rejected slices, or is used to indicate a slice of the rejected slices supported by each of the plurality of TAs, each of the plurality of TAs.
- TAs all belong to the first RA, and the plurality of TAs include the second TA.
- the advantage of the above setting is that since the amount of information in the first indication information becomes larger, the terminal device can learn that multiple rejected slices can be available in the second TA according to the first indication information. In this way, after moving to the second TA, the terminal device If the device wants to use at least one of the multiple rejected slices for communication, it can initiate a registration request again to request access to the corresponding slice.
- This can increase the number or types of network slices that terminal devices can use within the current wireless network coverage to a greater extent, meet the needs of terminal devices for communication by using network slices to a greater extent, and further improve user experience.
- the method before the terminal device receives the registration acceptance message from the core network device, the method further includes: the terminal device sends a message to the core network device.
- First capability indication information the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the method provided by the embodiment of the present application stipulates that the terminal device sends the first capability indication information to the AMF in advance to indicate whether it has the ability to receive the first indication information.
- the registration acceptance message sent by the AMF to the terminal device carries the first indication information.
- the first capability indication information may be explicitly (directly) indicated, for example, in accordance with protocol or system regulations, as a string of specific codes, or a bit of 0 or 1, or distinguished by NULL and non-NULL. or Alternatively, the first capability indication information may also be an implicit (indirect) indication, which is not limited in this application.
- the first capability indication information may include a bit of 1 to indicate that the terminal device has the ability to receive the first indication information, and a bit of 0 to indicate that the terminal device does not have the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- the first capability indication information may also be carried through other messages in the prior art, or the terminal device may separately send the first capability indication information to the AMF, which is not limited in this application.
- a communication method including: the terminal device sends a first registration request message to the core network device in the first tracking area TA;
- the terminal device receives a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is used to indicate Allow the terminal device to initiate a connection request to any one of the rejected slices in the second TA, where the rejected slices include the first slice;
- the terminal device When the terminal device moves from the first TA to the second TA, the terminal device sends a second registration request message to the core network device according to the first indication information.
- the second registration request The message includes information about the first slice.
- the registration acceptance message also carries a first indication message.
- the first indication message only indicates to the terminal device that the second TA may support one or more of the rejected slices without explicitly Indicates which specific one or which ones it supports.
- the terminal device triggers the registration process on its own and sends the registration request message to the AMF again (i.e., the second registration request message).
- the requested slice carried in the second registration request message includes the first slice, and after obtaining approval from the AMF, the terminal device can access the first slice for communication.
- the above settings can expand the number or types of network slices that the terminal device can use within the current wireless network coverage, and also increase the types of PDU sessions that the terminal device can establish, satisfying the needs of the terminal device through use to a greater extent.
- Network slicing is required for communication, thereby improving user experience.
- the method provided by this embodiment does not open the second TA's support information for rejected slices, and can ensure that the operator's slice deployment information will not be opened to the terminal device, which has higher security performance.
- the terminal device initiates a connection request to the first slice through the second registration request message in the second TA, it may be rejected because the second TA does not support the first slice.
- the first indication information includes an identification of the second TA.
- the first indication information includes a TA set
- the TA set includes allowing the terminal device to initiate a connection to any one of the rejected slices.
- the identity of the requested TA, and the TA set includes the second TA identity.
- the method before the terminal device receives the registration acceptance message from the core network device, the method further includes: the terminal device sends a message to the core network device.
- First capability indication information the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- a communication method including: the terminal device sends a first registration request message to the core network device in the first tracking area TA;
- the terminal device receives a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is used to indicate There is a mapping relationship between the first slice and the first network slice access layer group NSASG;
- the terminal device receives the information of the first NSASG through a broadcast message of the second TA of the first RA;
- the terminal device camps on the second TA, and sends a second registration request message to the core network device according to the first indication information, where the second registration request message includes the information of the first slice .
- the registration acceptance message also carries a first indication message.
- the terminal device can know in which NSASG corresponding TA a specific rejected slice is available. For example, according to the first indication information, the terminal can know that the rejected first slice is actually available in the second TA corresponding to the first NSASG, when the terminal device receives the information of the first NSASG through the broadcast message of the second TA. , the terminal can learn that the second TA can support the first slice.
- the terminal device can reside in the second TA, and again Initiate a registration request to request access to the first slice.
- the above settings can expand the number or types of network slices that the terminal device can use within the current wireless network coverage, and also increase the types of PDU sessions that the terminal device can establish, satisfying the needs of the terminal device through use to a greater extent. Network slicing is required for communication, thereby improving user experience.
- this method does not open the specific TA slice deployment situation to the terminal device. It only provides the mapping relationship between NSASG and rejected slices. When NSASG broadcast information is detected, a request for the rejected slice can be triggered without switching to The corresponding TA is triggered again. For example, it can only be located at the edge of the TA at this time, which is more flexible and applicable to more scenarios.
- the first indication information includes an identifier of the first slice and an identifier of the first NSASG.
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is the Any of multiple slices.
- the method before the terminal device receives the registration acceptance message from the core network device, the method further includes: the terminal device sends a message to the core network device.
- First capability indication information the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- the fourth aspect provides a communication method, including:
- the core network device receives the first registration request message from the terminal device;
- the core network device sends a registration acceptance message to the terminal device, and the registration acceptance message includes a rejection information of the slice, information of the first registration area RA and first indication information,
- the first indication information is used to indicate that the second TA supports the first slice, the second TA belongs to the first RA, and the first slice belongs to the rejected slice; or,
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices in the second TA, and the rejected slices include the first slice; or,
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first network slice access layer group NSASG;
- the core network device receives a second registration request message from the terminal device, where the second registration request message includes information about the first slice.
- the first indication information includes an identifier of the second TA and an identifier of the first slice; or, the first indication information includes the The identifier of the second TA; or, the first indication information includes the identifier of the first slice and the identifier of the first NSASG.
- the first indication information includes support information of multiple TAs for the rejected slices, and the support information is used to indicate each of the multiple TAs.
- the TA supports at least one of the rejected slices, or is used to indicate a slice of the rejected slices supported by each of the plurality of TAs, each of the plurality of TAs. Belonging to the first RA, the plurality of TAs include the second TA; or,
- the first indication information includes a TA set, the TA set includes an identification of a TA that allows the terminal device to initiate a connection request to any one of the rejected slices, and the TA set includes the second TA. logo; or,
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is any one of the multiple slices.
- the method further includes: the core network device receiving first capability indication information from the terminal device, the first capability indication information being used to indicate The terminal device has the ability to receive the first indication information; the core network device sending a registration acceptance message to the terminal device includes: the core network device sends a registration acceptance message to the terminal device according to the first capability indication information. The registration accepts the message.
- the first capability indication information is carried in the first registration request message.
- the method before the core network device sends a registration acceptance message to the terminal device, the method further includes:
- the core network device determines that the second TA belongs to the first RA and supports at least one of the rejected slices.
- the fifth aspect provides a communication method, including:
- the core network device receives the first registration request message from the terminal device;
- the core network device obtains first capability indication information, and the first capability indication information is used to indicate whether the terminal device has the ability to receive the first indication information;
- the core network device sends a registration acceptance message to the terminal device, where the registration acceptance message includes the rejected slice.
- the registration acceptance message includes the rejected slice.
- the first indication information is used to indicate that the second tracking area TA supports the first slice, the second TA belongs to the first RA, the The first slice belongs to the rejected slice; or,
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices in the second TA, and the rejected slices include the first slice; or,
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first network slice access layer group NSASG;
- the core network device sends a registration acceptance message to the terminal device, where the registration acceptance message includes information about the rejected slice. and information about the second RA. No TA in the second RA supports the rejected slice.
- the first indication information includes the identification of the second TA and the identification of the first slice; or,
- the first indication information includes the identification of the second TA; or,
- the first indication information includes the identifier of the first slice and the identifier of the first NSASG.
- the first indication information includes support information of multiple TAs for the rejected slices, and the support information is used to indicate each of the multiple TAs.
- the TA supports at least one of the rejected slices, or is used to indicate a slice of the rejected slices supported by each of the plurality of TAs, each of the plurality of TAs. Belonging to the first RA, the plurality of TAs include the second TA; or,
- the first indication information includes a TA set, the TA set includes an identification of a TA that allows the terminal device to initiate a connection request to any one of the rejected slices, and the TA set includes the second TA. logo; or,
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is any one of the multiple slices.
- the first capability indication information is carried in the first registration request message.
- a sixth aspect provides a terminal device, including:
- a sending module configured to send a first registration request message to the core network device when the terminal device is within the first tracking area TA;
- a receiving module configured to receive a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is used to Indicate that the second TA supports the first slice, the second TA belongs to the first RA, and the first slice belongs to the rejected slice;
- the sending module is also configured to send a second registration request message to the core network device according to the first indication information when the terminal device moves from the first TA to the second TA.
- the second registration request message includes information about the first slice.
- the first indication information includes an identifier of the second TA and an identifier of the first slice.
- the first indication information includes support information of multiple TAs for the rejected slice, and each TA among the multiple TAs belongs to the The first RA supports at least one slice among the rejected slices, and the second TA is any one of the plurality of TAs.
- the sending module before the receiving module receives the registration acceptance message from the core network device, the sending module is further configured to send a first message to the core network device. Capability indication information, the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- a terminal device including:
- a sending module configured to send a first registration request message to the core network device when the terminal device is in the first tracking area TA;
- a receiving module configured to receive a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is used to Instructing the terminal device to allow initiating a connection request to any one of the rejected slices in a second TA, which belongs to the first RA and supports at least one of the rejected slices.
- the rejected slice includes the first slice;
- the sending module is also configured to, when the terminal device moves from the first TA to the second TA, send a second registration request message to the core network device according to the first indication information, the The second registration request message includes information about the first slice.
- the first indication information includes an identification of the second TA.
- the first indication information is used to indicate that the terminal device is allowed to initiate a response to any of the rejected slices in any TA in the TA set.
- a slice connection request each TA in the TA set supports at least one slice in the rejected slices, and the second TA is any one in the TA set.
- the sending module before the receiving module receives the registration acceptance message from the core network device, the sending module is further configured to send a first message to the core network device. Capability indication information, the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- a terminal device including:
- a sending module configured to send a first registration request message to the core network device when the terminal device is within the first tracking area TA;
- a receiving module configured to receive a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is used to Indicates that there is a mapping relationship between the first slice and the first network slice access layer group NSASG, the first slice belongs to the rejected slice, and the first RA includes the second TA;
- the receiving module is also configured to receive the information of the first NSASG through the broadcast message of the second TA;
- the sending module is also configured to send a second registration request message to the core network device when the terminal device resides on the second TA according to the first indication information.
- the second registration request message Contains information about the first slice.
- the first indication information includes an identifier of the first slice and an identifier of the first NSASG.
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is the Any of multiple slices.
- the sending module before the receiving module receives the registration acceptance message from the core network device, the sending module is further configured to send a first message to the core network device. Capability indication information, the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- a core network device including:
- a receiving module configured to receive the first registration request message from the terminal device
- a sending module configured to send a registration acceptance message to the terminal device, where the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information,
- the first indication information is used to indicate that the second TA supports the first slice, the second TA belongs to the first RA, and the first slice belongs to the rejected slice; or,
- the first indication information is used to instruct the terminal device to allow initiating a connection request for any one of the rejected slices in the second TA, which belongs to the first RA and supports the at least one of the rejected slices, the rejected slices including the first slice; or,
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first network slice access layer group NSASG, the first slice belongs to the rejected slice, and the first RA includes the Two TA;
- the receiving module is also configured to receive a second registration request message from the terminal device, where the second registration request message includes the information of the first slice.
- the first indication information includes an identifier of the second TA and an identifier of the first slice; or, the first indication information includes the The identifier of the second TA; or, the first indication information includes the identifier of the first slice and the identifier of the first NSASG.
- the first indication information includes support information of multiple TAs for the rejected slice, and each of the multiple TAs belongs to the The first RA supports at least one of the rejected slices, and the second TA is any one of the plurality of TAs; or,
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices in any TA in the TA set, and each TA in the TA set is allowed to initiate a connection request to any slice in the rejected slice.
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is any one of the multiple slices.
- the receiving module is further configured to receive first capability indication information from the terminal device, where the first capability indication information is used to indicate to the terminal The device has the ability to receive the first indication information;
- the sending module is specifically configured to send the registration acceptance message to the terminal device according to the first capability indication information.
- the first capability indication information is carried in the first registration request message.
- a core network device including:
- a receiving module configured to receive a first registration request message from a terminal device, where the first registration request message includes first capability indication information, and the first capability indication information is used to indicate whether the terminal device is capable of receiving the first indication. information capabilities;
- a sending module when the first capability indication information indicates that the terminal device has the ability to receive the first indication information, is configured to send a registration acceptance message to the terminal device, where the registration acceptance message includes information about the rejected slices, Information about the first registration area RA and first indication information.
- the first indication information is used to indicate that the second tracking area TA supports the first slice.
- the second TA belongs to the first RA.
- the first slice The slice belongs to the rejected slice; or,
- the first indication information is used to instruct the terminal device to allow initiating a connection request for any one of the rejected slices in the second TA, which belongs to the first RA and supports the at least one of the rejected slices, the rejected slices including the first slice; or,
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first network slice access layer group NSASG, the first slice belongs to the rejected slice, and the first RA includes the Two TA;
- the sending module is configured to send a registration acceptance message to the terminal device, where the registration acceptance message includes the rejected slice. information and the information of the second RA. None of the TAs in the second RA supports the rejected slice.
- the first indication information includes an identifier of the second TA and an identifier of the first slice; or, the first indication information includes the The identifier of the second TA; or, the first indication information includes the identifier of the first slice and the identifier of the first NSASG.
- the first indication information includes support information of multiple TAs for the rejected slices, and each TA among the multiple TAs belongs to the first RA and supports at least one of the rejected slices, and the second TA is any one of the plurality of TAs; or,
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices in any TA in the TA set, and each TA in the TA set is allowed to initiate a connection request to any slice in the rejected slice.
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is any one of the multiple slices.
- inventions of the present application provide a communication device.
- the communication device may be a terminal device, or a chip provided in the terminal device.
- the communication device includes: a processor, a memory and a transceiver;
- Transceivers are used to receive and send messages
- Memory is used to store instructions
- the processor is configured to execute instructions stored in the memory.
- the communication device is caused to execute the method executed in any one of the aforementioned first to third aspects.
- inventions of the present application provide a communication device.
- the communication device may be a core network device, or a chip provided in the core network device.
- the communication device includes: a processor, a memory and a transceiver;
- Transceivers are used to receive and send messages
- Memory is used to store instructions
- the processor is configured to execute instructions stored in the memory.
- the communication device is caused to execute the method performed in any one of the foregoing fourth to fifth aspects.
- a terminal device including at least one processor, the at least one processor being coupled to a memory, reading and executing instructions in the memory, to implement the foregoing first to third aspects.
- the method executed by any of the implementation methods.
- the terminal device also includes the memory.
- a core network device including at least one processor, the at least one processor being coupled to a memory, reading and executing instructions in the memory, to implement the fourth to fifth aspects.
- the method executed by any of the implementation methods.
- the terminal device also includes the memory.
- a computer program product includes: computer program code.
- the computer program code When the computer program code is run on a computer, it causes the computer to execute any of the above-mentioned first to fifth aspects. A method performed by an implementation.
- the above computer program code can be stored in whole or in part on the first storage medium, where the first storage medium can be packaged together with the processor, or can be packaged separately from the processor. This application does not specifically limit this. .
- a computer-readable medium stores program code.
- the computer program code When the computer program code is run on a computer, it causes the computer to execute the above-described first to fifth aspects. Methods executed by any implementation.
- a chip system including a processor for calling and running a computer program from a memory, so that the communication device installed with the chip system executes and causes the computer to execute the above-mentioned first to fifth aspects.
- An eighteenth aspect provides a communication system, which includes at least one of the terminal equipment provided in the first to third aspects, and the core network equipment provided in the fifth or sixth aspect.
- Figure 1 is a schematic diagram of the network architecture of the 5G communication system.
- Figure 2 is a schematic diagram of an example of network slicing.
- Figure 3 is a schematic diagram of the slice selection process of the terminal device during the registration process.
- Figure 4 is a schematic diagram of a possible application scenario of the present application.
- FIG. 5 is a schematic flow chart of an example of a communication method provided by an embodiment of the present application.
- Figure 6 is a schematic flow chart of another example of the communication method provided by the embodiment of the present application.
- FIG. 7 is a schematic flow chart of yet another example of the communication method provided by the embodiment of the present application.
- FIG. 8 is a schematic flow chart of yet another example of the communication method provided by the embodiment of the present application.
- Figure 9 is a schematic flow chart of yet another example of the communication method provided by the embodiment of the present application.
- Figure 10 is a schematic block diagram of a terminal device provided by an embodiment of the present application.
- Figure 11 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
- Figure 12 is a schematic block diagram of a core network device provided by an embodiment of the present application.
- Figure 13 is a schematic structural diagram of a core network device provided by an embodiment of the present application.
- GSM global system for mobile communications
- CDMA code division multiple access
- WCDMA broadband code division multiple access
- GPRS general packet radio service
- LTE long term evolution
- FDD frequency division duplex
- TDD LTE Time division duplex
- UMTS universal mobile telecommunication system
- WiMAX global interoperability for microwave access
- 5G fifth generation
- NR new radio access technology
- 6G sixth generation
- FIG. 1 is a schematic diagram of the network architecture of the 5G communication system.
- the figure shows some network elements in the 5G architecture.
- the network architecture includes terminal equipment, access network equipment, access management network elements, network slice selection network elements, data management network elements and network storage network elements. The following is The functions of each device or network element are briefly introduced and explained.
- the terminal device in this application is a device with wireless transceiver functions, and may also be called user equipment (UE).
- Terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons, satellites, etc.).
- the terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal, an augmented reality (AR) terminal, or an industrial control (industrial control) Wireless terminals in autonomous driving (self driving), wireless terminals in remote medical (remote medical), wireless terminals in smart grid (smart grid), wireless terminals in transportation safety (transportation safety), smart Wireless terminals in smart cities, wireless terminals in smart homes, etc.
- the access network device in this application is a device that provides wireless communication functions for terminals, and may also be called a radio access network (radio access network, RAN) device.
- Access network equipment includes but is not limited to: next-generation base station (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B, NB), base station controller (base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or homenode B, HNB), baseband unit (baseBand unit (BBU)), transmission point (transmitting and receivingpoint, TRP) , transmitting point (TP), mobile switching center, etc.
- gnodeB, gNB next-generation base station
- eNB evolved node B
- RNC radio network controller
- node B, NB node B
- BSC base station controller
- BTS base transceiver station
- the access management network element is a control plane network element provided by the operator's network. It is responsible for access control and mobility management of terminal devices accessing the operator's network. For example, it includes mobility status management, allocation of user temporary identities, authentication and user and other functions.
- the access management network element may be an access and mobility management function (AMF) network element.
- AMF access and mobility management function
- the access management network element can still be an AMF network element, or it can also have other names, which is not limited in this application.
- Network slice selection network elements can be used to select appropriate network slices for terminal services.
- the network slice selection network element may be a network slice selection function (NSSF) network element.
- NSSF network slice selection function
- future communication systems such as 6G
- network open function network elements can still be NSSF network elements, or they can have other names, which are not limited in this application.
- the data management network element is used to generate authentication credentials, user identification processing (such as storing and managing user permanent identities, etc.), access control and contract data management, etc.
- the data management network element may be a unified data management (UDM) network element.
- UDM unified data management
- the data management network element can still be a UDM network element, or it can also have other names, which is not limited in this application.
- Network storage network elements can be used to provide network element discovery functions and provide network element information corresponding to network element types based on requests from other network elements.
- Network storage network elements can also be used to provide network element management services, such as network element registration, update, de-registration, network element status subscription and push, etc.
- the network storage network element may be a network repository function (NRF) network element.
- NRF network repository function
- network storage network elements can still be NRF network elements, or they can have other names, which are not limited in this application.
- the session management function (SMF) network element is mainly used for session management, UE Internet Protocol (IP) address allocation and management, and selection of endpoints that can manage user plane functions, policy control, or charging function interfaces. And downstream data notifications, etc. In the embodiment of this application, it can be used to implement the function of the session management network element.
- SMF session management function
- the terminal device described in the embodiment of this application may be the UE described in Figure 1, and the access network device described in the embodiment of this application may be the RAN described in Figure 1.
- the access management network element described in the embodiment of this application may be the AMF network element shown in Figure 1, or may be a network element in a future communication system that has the functions of the above-mentioned AMF network element.
- the network slicing selection network element described in the embodiment of the present application may be the NSSF network element shown in Figure 1, or may be a network element in the future communication system that has the functions of the above-mentioned NSSF network element.
- the data management network element described in the embodiment of the present application may be the UDM network element shown in Figure 1, or may be a network element in a future communication system that has the functions of the above-mentioned UDM network element.
- the network storage network element described in the embodiment of this application may be the NRF network element shown in Figure 1, or may be a network element in a future communication system that has the functions of the above-mentioned NRF network element.
- the session management function network element described in the embodiment of this application may be the SMF network element shown in Figure 1, or may be a network element in a future communication system that has the functions of the above-mentioned SMF network element.
- the access management network element is the AMF network element
- the network slicing selection network element is the NSSF network element
- the data management network element is the UDM network element
- the network storage network element is the NRF network element
- the session management function The network element is SMF as an example for explanation.
- the AMF network element is abbreviated as AMF
- the NSSF network element is abbreviated as NSSF
- the UDM network element is referred to as UDM
- the NRF network element is referred to as NRF
- the SMF network element is referred to as SMF
- the terminal equipment is referred to as UE
- the access network equipment is referred to as RAN.
- the AMF described later in this application can be replaced by the access management network element
- the NSSF can be replaced by the network slicing selection network element
- the UDM can be replaced by the data management network element
- the NRF can be replaced by the network storage network element
- the SMF All can be replaced by session management function network elements
- RAN can be replaced with access network equipment
- UE can be replaced with terminal equipment.
- network slicing and “slicing” are the same concept and refer to the same content. If one of the descriptions is used in different places, the two can be interchanged.
- the embodiments of the present application can be applied to various communication systems that support network slicing, such as 5G communication systems.
- system is interchangeable with "network”.
- the system architecture described in the embodiments of this application is to more clearly explain the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided by the embodiments of this application. Persons of ordinary skill in the art will know that with the evolution of network architecture, , the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
- 5G network slicing technology provides mutually isolated network environments for different application scenarios by virtualizing independent logical networks on the same network infrastructure, so that different application scenarios can customize network functions and functions according to their own needs.
- QoS quality of service
- the goal of 5G network slicing is to organically combine terminal equipment, access network resources, core network resources, and network operation and management systems to provide different business scenarios or business types with a complete and mutually isolated network that can be independently operated and maintained. network.
- Figure 2 is a schematic diagram of network slicing.
- Figure 2 includes three network slices, namely critical machine type of communication (MTC) slice, massive MTC slice and mobile broadband (MBB) slice.
- MTC critical machine type of communication
- MBB mobile broadband
- the terminal devices corresponding to the critical MTC slice can include vehicles, etc.
- the terminal devices corresponding to the massive MTC slice can include some measurement meters, such as electricity meters or gas meters
- the terminal devices corresponding to the MBB slice can include mobile phones or personal computers ( personal computer, PC), etc.
- 3GPP 3rd generation partnership project
- the network slice selection process will be triggered when the terminal device is initially attached to the network.
- the selection process of network slicing depends on one or more parameters such as the user's subscription data, local configuration information, roaming agreement, or operator's policy. In the selection process of network slicing, the above parameters need to be considered comprehensively to provide the best solution for the network slicing.
- the terminal device selects the best slice type.
- the terminal can provide the requested network slice to the core network, which is used by the core network to select a network slice instance for the terminal.
- the network slice requested by the terminal can be represented by the requested network slice selection assistance information (requestedNSSAI).
- Requested NSSAI is composed of one or more single network slice selection assistance information (single network slice selection assistance information, S-NSSAI), that is, NSSAI is a set of S-NSSAI.
- S-NSSAI single network slice selection assistance information
- Each S-NSSAI is used to identify a network slice type. It can also be understood that the S-NSSAI is used to identify the network slice, or it can be understood that the S-NSSAI is the identification information of the network slice. In the description of this application, multiple means two or more, for example, it can be 3, 4 or 5.
- a network slice is identified by S-NSSAI, which consists of slice type/service type (SST) and slice differentiator (SD).
- SST slice type/service type
- SD slice differentiator
- SST is used to describe the characteristics and business characteristics of the slice, indicating the characteristics and services that the network is expected to provide.
- SD can be used as complementary information to SST when selecting network slice instances (NSI). For example, when SST points to multiple NSIs, SD can further divide these NSIs. That is, SD is used as optional information to distinguish different network slices with the same SST characteristics.
- FIG. 3 is a schematic diagram of the slice selection process of the terminal device during the registration process.
- the terminal device makes a slice request when registering, and the core network device feeds back the allowed slices (allowedNSSAI) that it can use to the terminal device.
- the core network device feeds back the allowed slices (allowedNSSAI) that it can use to the terminal device.
- the allowed slices allowedNSSAI
- subsequent terminal devices perform services, they can only use the allowed slices.
- PDU packet data unit
- Step 1 The UE sends a registration request message to the RAN, and the RAN receives the registration request message from the UE.
- the registration request message carries a requested slice (requestedNSSAI), and the requested slice is a network slice of the PDU session that the terminal device expects to establish.
- the requested slice is used to indicate the network slice provided by the terminal device to the serving public land mobile network during the registration process.
- the requested slice is the slice that the UE determines to support when signing up.
- the requested slice includes one or more slices (S-NSSAI), and one S-NSSAI can be used to identify a network slice.
- Step 2 RAN sends the registration request to the initial AMF, and the initial AMF receives the registration request message from the RAN.
- the RAN forwards the registration request message to the initial AMF.
- the registration request message is, for example, an N1 message.
- the N1 message may include information such as N1 parameters, registration message, access information of the terminal device, PDU session information, and context request of the UE.
- Step 3 The initial AMF initiates a request to the UDM to obtain the UE's subscription information, which includes the UE's subscription NSSAI and other information.
- Step 4 If the initial AMF cannot determine the allowed slices for the UE, it requests slice selection from the NSSF, and sends the slices requested by the UE, the slices subscribed by the UE, and the location information of the UE to the NSSF.
- Step 5 NSSF determines the slices allowed by the UE.
- NSSF also needs to determine the target AMF.
- NSSF sends the allowed slices, the set/list of target AMFs, and the identification (identification, ID) of the NRF corresponding to the target AMF to the initial AMF.
- the allowed slices are used to indicate where the UE is in the current registration area (RA). There are slices that can be used across the tracking area (TA). The allowed slices include at least one slice included in the requested slices.
- the core network device may also maintain a network slice that denies UE access.
- This part of the network slice may be called a rejected slice (rejectedNSSAI), which may include one or more slices (S-NSSAI).
- the slices in the rejected slices can be network slices that are not supported by the current network or the current TA.
- the rejected slice is generally determined based on the requested slice carried in the UE registration request. When the UE requests access to a certain network slice, if the current network or the current TA does not support the network slice, the network slice will be added. into the rejected slice list.
- TA is the basic unit of location management in the communication system and consists of one or more cells.
- a cell is an area covered by a wireless access network device or a part of an area covered by a wireless access network device.
- TA may include cells included by multiple wireless access network devices.
- One network slice can provide services for one or more TAs, and one TA can support one or more network slices.
- TA can be identified by tracking area identifier (TAI) or tracking area code (TAC).
- TAI includes mobile country code (MCC), mobile network code (mobile network code, MNC) and TAC.
- RA consists of one or more TAs. For example, when the terminal device moves among different TAs in the same RA, it does not need to perform mobility registration update. Mobility registration update only needs to be performed when the terminal device moves to a new TA and it is determined that the new TA does not belong to the RA.
- Step 6 If an AMF needs to be switched, the initial AMF queries the corresponding NRF for relevant information about the target AMF based on the NRF identifier sent by the NSSF.
- Step 7a The initial AMF sends an AMF reset (relocation) request message to the target AMF.
- the reset request message is used to request to reset (update) the AMF for the UE.
- the AMF reset request message carries indication information of allowed slices.
- step 7a can be replaced by step 7b as shown in Figure 3.
- the initial AMF may also send an AMF reset request message to the target AMF via the RAN.
- the AMF reset request message also carries indication information of allowed slices.
- Step 8 The target AMF sends a registration accept message to the RAN, and the RAN receives the registration accept message from the target AMF.
- the registration accept message is used to notify the UE that the registration request is accepted.
- the registration acceptance message includes relevant information such as allowed slices, RA allocated to the UE, and rejected slices.
- the target AMF sends the registration acceptance message to the RAN through an N2 message.
- the target AMF can allocate RA to the UE according to the allowed slices.
- AMF can query the network slices supported by each of the multiple surrounding TAs, and AMF will form the RA of the UE from multiple TAs that support allowed slices.
- Table 1 shows the support of different TAs for network slicing.
- NSSF determines that the allowed slices only include slice #1.
- AMF can query the network supported by each of the multiple surrounding TAs.
- three TAs ie, TA#1, TA#2, and TA#3 that support slice #1 are formed into RA#1, which is the registration area allocated by the core network to the UE.
- TA#4 cannot be divided because it does not support slice #1. Allocated to RA#1.
- Step 9 RAN sends the registration acceptance message to the UE, and the UE receives the registration acceptance message from the RAN. That is, the RAN forwards the aforementioned registration acceptance message to the UE.
- the UE may not need to switch AMF.
- the aforementioned steps 6 and 7 can be omitted.
- the initial AMF may send the aforementioned registration acceptance message to the RAN, and the RAN forwards the registration acceptance message to the UE.
- the terminal device may initiate the registration process to the core network in the following five scenarios:
- the terminal device registers to the 5G network for the first time
- the UE will only perform network slice selection during the registration process, and the conditions for the UE to trigger the registration process are only the above five situations, so the only scenarios where the UE can perform allowed NSSAI slice selection are the above scenarios.
- Figure 4 is a schematic diagram of a possible application scenario of the present application. Based on the current protocol, as shown in Figure 4, the following scenarios may exist:
- TA#1 supports slice #1
- TA#2 supports slice #1 and slice #2.
- TA#1 supports slice #1, which can be understood as slice #1 is available in TA#1
- TA#2 supports slice #1 and slice #2, which can be understood as slice #1 and slice #2 are available in TA#2.
- the UE accesses the network in TA#1 and performs the registration process.
- the slices requested by the UE are slice #1 and slice #2. However, because TA#1 only supports slice #1, the allowed slice is slice #1 and rejected.
- Slice I is slice #2.
- RA#1 is the registration area allocated by the core network to the UE, RA# 1 includes at least multiple TAs including TA#1 and TA#2.
- the UE moves within RA#1.
- TA#2 also supports slice #2.
- the UE does not leave RA.
- the registration process will not be reinitiated, so slice #2 will still not be accessed.
- the UE will not request to establish a session for slice #2. If the UE still wants to access slice #2, the UE needs to move to the range of TA#3 which is outside the range of RA#1 and supports slice #2. Only then can the UE re-initiate the registration process and try to access slice #2.
- the other part of the slices included in the slices requested by the terminal device are not among the allowed slices. , so that even if the end device is in a TA that supports the use of another part of the slice (i.e. the rejected slice) During this time, the terminal device is not allowed to use the other part of the slice.
- This method limits the number or type of network slices that the terminal device can use within the current network coverage, and also limits the types of PDU sessions that the terminal device can establish. It cannot meet the needs of the terminal device for communication by using network slices. .
- embodiments of the present application provide a communication method, terminal equipment, and core network equipment, which can expand the number or types of network slices that the terminal equipment can use within the current network coverage, and also increase the number of network slices that the terminal equipment can establish.
- the type of PDU session can meet the communication needs of terminal devices through the use of network slicing to a greater extent, thereby improving user experience.
- the terminal equipment and/or the core network equipment can perform some or all of the steps in the embodiment of the present application. These steps or operations are only examples.
- the embodiment of the present application can also Perform other operations or variations of various operations.
- various steps may be performed in a different order than those presented in the embodiments of the present application, and it may not be necessary to perform all operations in the embodiments of the present application.
- the core network device may include only one core network element (such as AMF), or may be composed of multiple core network elements (such as at least two of the aforementioned initial AMF, target AMF, and NSSF). This application will No special restrictions are made.
- FIG. 5 is a schematic flow chart of the communication method 500 provided by this application.
- the communication method 500 provided by the embodiment of the present application is described below with reference to Figure 5.
- the method 500 includes:
- Step 501 The terminal device sends a first registration request message to the AMF in the first tracking area TA, and the AMF receives the first registration request message from the terminal device.
- the method 500 provided in the embodiment of this application can be applied to the scenario where the terminal device initiates a registration process to the core network.
- the conditions for the terminal device to trigger the registration process can be any one of the five conditions mentioned above. For example, the terminal device moves to a TA outside the original registration area RA (i.e. the first TA), causing a mobility registration update, so it needs to Initiate a new registration process to the core network.
- the conditions for the terminal device to trigger the registration process are not limited to the above five. With the continuous evolution of 3GPP standards, the registration process can also be triggered by any other conditions in the future.
- the terminal device accesses the network through the cell in the first TA and performs a registration process.
- the terminal device may send a first registration request message to the AMF via a radio access network device (RAN).
- RAN radio access network device
- the AMF receives the registration request message via the radio access network device.
- the registration request message here may also be named by other names in the future, which is not limited in the embodiment of this application.
- the first registration request message includes information about the requested slice (requested NSSAI).
- the requested slice may include multiple slices.
- the first registration request message may include identifiers corresponding to multiple slices (such as SST and SD).
- the first registration request message is, for example, an N1 message, that is, the terminal device can send the first registration request message to the AMF through the N1 interface.
- Step 502 AMF determines allowed slices (allowedNSSAI) and rejected slices (rejectedNSSAI).
- the AMF After receiving the first registration request message, the AMF performs slice selection for the terminal device. AMF makes a comprehensive judgment based on the terminal device's subscription data, requested slices, roaming agreement, local configuration and other information, and selects allowed slices and rejected slices for the terminal device.
- AMF may determine a set of one or more slices in the requested slices as allowed slices, that is, the allowed slices may be a subset or a full set of slices included in the requested slices. On this basis, AMF can determine the set of remaining slices in the requested slice as rejected slices. For example, a slice among the requested slices that is not supported by the current TA (ie, the first TA) may be determined as a rejected slice.
- Table 2 is a table of correspondences between different types of slices and specific slices.
- the terminal device located in TA #1 ie the first TA
- the first registration request message includes the requested slice.
- the requested slice includes slice #1 and slice #2.
- AMF determines that TA#1 where the terminal is currently supports only slice #3 and does not support the other two. Therefore, slice #3 is determined to be an allowed slice, while slice #1 and slice #2 These two slices together form the rejected slice. That is, slice #1 and slice #2 are both rejected slices.
- Step 503 AMF allocates the first registration area RA as the current RA of the terminal device according to the allowed slices.
- the AMF may allocate RA to the terminal device according to allowed slices.
- the AMF may query the slices supported by each of the multiple TAs surrounding the first TA, and the AMF forms the first RA from multiple TAs that support at least one slice among the allowed slices, and allocates them to the terminal device. That is, for each TA in the first RA, at least one slice among the allowed slices should be supported.
- a certain TA supports a certain slice, which can also be understood to mean that the slice is available within the TA. If TA does not support a certain slice, it can also be understood that the slice is not available in the TA.
- Table 2 also shows the support for slicing by different TAs queried by AMF.
- AMF queried a total of 7 TAs including TA#1 ⁇ TA#7.
- TA#1 is the TA from which the terminal initiates the registration request, that is, TA#1 is the first TA.
- AMF determines that the allowed slices only include slice #3.
- the TAs that support slice #3 are TA#2 ⁇ TA#5, so AMF will A total of five TAs, TA#1 to TA#5, form the first RA. Since TA#6 and TA#7 do not support slice #3, they cannot be allocated to the first RA.
- the AMF can query the NSSF or other core network elements for information about the TA and the network slices that can be used in the TA.
- the AMF may not be able to complete the above steps 502 and 503 independently. In this case, it can be completed with the help of network elements such as NSSF and UDM. For example, at least one of the above steps may complete It is all done by NSSF, and NSSF can inform AMF of the corresponding results. For details, please refer to the aforementioned description of steps 4 and 5.
- the AMF, NSSF, and UDM jointly complete slice selection and allocate RA to the terminal device, which is an existing technology and will not be described again here.
- AMF can also interact with NSSF to obtain information about allowed slices and rejected slices from NSSF.
- the decision-making network element is NSSF, and AMF can receive and forward the message.
- Step 504 The AMF sends a registration acceptance message to the terminal device, and the terminal device receives the registration acceptance message from the AMF.
- the registration acceptance message may include information about allowed slices, information about rejected slices, and information about the first RA.
- This registration request message is used to respond to the first registration request message.
- the AMF may carry the above information in the registration acceptance message and send it to the terminal device through the registration acceptance message.
- the AMF may send a registration accept message to the terminal device via the Radio Access Network Equipment (RAN).
- RAN Radio Access Network Equipment
- the terminal device receives the registration acceptance message via the radio access network device.
- the registration acceptance message here may also be named by other names in the future, which is not limited in the embodiment of this application.
- the registration acceptance message may be, for example, an N2 message, that is, the AMF may send the registration acceptance message to the terminal device through the N2 interface.
- the allowed slices may include one or more slices, and the registration acceptance message may include the identification information of the one or more slices.
- the allowed slices include slice #3, then the corresponding information element (or bit) of the registration acceptance message may carry the identifier of slice #3.
- the identifier may be S-NSSAI.
- the rejected slices may include one or more slices, and the registration acceptance message may include the identification information of the one or more slices.
- the rejected slices include slice #1 and slice #2, then the corresponding information element (or bit) of the registration acceptance message can carry the identifiers of slice #1 and slice #2, for example, the identifier can be S-S- NSSAI.
- the first RA includes multiple TAs including the first TA, and the information of the first RA may include identification information of each of the multiple TAs included in the first RA.
- the identifier of the TA may be, for example, TAI or TAC.
- the information of the first RA may include the identifiers of TA#1 to TA#5, that is, the corresponding information elements (or bits) of the registration acceptance message may carry the identifiers of TA#1 to TA#5.
- the registration acceptance message in the embodiment of the present application also carries first indication information.
- the first indication information is used to indicate that the second TA supports the first slice. TA belongs to one of the first RA and the first slice belongs to one of the rejected slices.
- the first indication information may be determined and generated by the AMF itself, or may be determined and generated by the NSSF, which is not specifically limited in this application.
- the NSSF may determine and generate relevant information such as allowed slices, rejected slices, and the first RA, while the first indication information is generated by the AMF and added to the registration acceptance message.
- Step 505 The terminal device continues other registration processes to complete the registration. At this time, the terminal device can use one or more slices among the allowed slices to establish a PDU session (PDU session). Of course, if the terminal device does not currently have business requirements, it does not need to use the slices in the allowed slices.
- Step 506 When the terminal device moves from the first TA to the second TA, the terminal device may send a second registration request message to the AMF according to the first indication information, and the second registration request message includes the information of the first slice.
- the terminal device when the terminal device moves from the first TA to the second TA, and the terminal device determines that it needs to access the first slice according to current business requirements (such as the usage requirements of a certain application (application, APP))
- the terminal device can learn that the second TA currently located supports the first slice, because the first slice is refused to be used in the current RA (first RA).
- the terminal device triggers the registration process by itself and sends the registration request message to the AMF again (i.e., the second registration request message).
- the requested slice carried in the second registration request message includes the first slice.
- the terminal device can access the first slice for communication.
- the second registration request message includes the identifier of the first slice.
- the identifier may be the S-NSSAI of the first slice.
- the registration acceptance message also carries a first indication message.
- the terminal device can know in which TA a specific rejected slice is available.
- the first indication information allows the terminal to know that the rejected first slice is actually available in the second TA, so that after the terminal device moves to the second TA, if it still wants to use the first slice for network communication (for example, establishing PDU session), you can initiate a registration request again to request access to the first slice.
- the above settings can expand the number or types of network slices that the terminal device can use within the current wireless network coverage, and also increase the types of PDU sessions that the terminal device can establish, satisfying the needs of the terminal device through use to a greater extent.
- Network slicing is required for communication, thereby improving user experience.
- the first slice is slice #1 in Table 2
- the second TA is TA#2 in Table 2.
- the first indication information indicates to the terminal device TA#2 that Supports slice #1, that is, slice #1 is available in TA #2.
- the terminal device moves from TA#1 that sent the first registration request message to TA#2 (it can stay or pass through other TAs during the period), if the terminal device still wants to access slice #1 due to business needs, it can Initiate a registration request again to request access to slice #1.
- the terminal device moves from the first TA to the second TA, if the terminal device determines that it wants to access other slices in addition to the first slice, at this time, the requested slice in the second registration request message will be in addition to the first slice.
- other slices may also be included, which is not specifically limited in this application.
- the terminal device when the terminal device moves from the first TA to the second TA, if the terminal device determines that there is no current need to access the first slice (does not want to use the first slice), it may not send the second slice to the AMF. Registration request message, that is, the terminal device may not take any action at this time, and step 506 may be omitted.
- the communication method 500 in the embodiment of the present application actually provides another condition that can trigger the terminal device to initiate a registration process with the core network. That is, in addition to the aforementioned five conditions, the communication method 500 provided by the embodiment of the present application can be used as the sixth condition for the terminal device to trigger the registration process.
- step 501 in method 500 that is, the terminal device sends a first registration request message to the AMF, may also be a registration process automatically triggered by the terminal device according to the first instruction message. That is, in step 501, if the terminal device wants to use a slice that was previously rejected in the RA, and the terminal knows that the first TA currently located supports the rejected slice, it sends a first registration request message to request access. The slice was rejected.
- the first indication information may be carried in the registration acceptance message as an independent information element, and the first indication information may include the identity of the second TA and the identity of the first slice.
- the identifier of the second TA may be the TAI or TAC of the second TA
- the identifier of the first slice may be the S-NSSAI of the first slice.
- the information of the rejected slice, the information of the first RA, and the first indication information can be carried in the registration accept message as three independent information elements, or two or three of them can also be carried. are carried in the same cell (the advantage is that it helps reduce the size of the entire registration acceptance message). In other words, its Two or three pieces of information in may share one information element, and this application does not place any special restrictions on the specific implementation method of the registration acceptance message.
- the second TA may be any one of multiple TAs within the first RA that supports at least one of the rejected slices.
- the second TA may be any one of TA#2, TA#3, and TA#5.
- the second TA may support only one slice among the rejected slices, in which case the first slice is the only slice supported by the second TA.
- the second TA may be TA#2.
- TA#2 only supports slice #1 among the rejected slices.
- the first slice is slice #1.
- the second TA may be TA#3.
- TA#3 only supports slice #2 among the rejected slices.
- the first slice is slice #2.
- the second TA may support multiple slices among the rejected slices, and then the first slice may be any one of the multiple slices supported by the second TA.
- the second TA can be TA#5, and TA#5 supports slice #1 and slice #2 among the rejected slices.
- the first slice can be slice #1 or slice #2. .
- the first indication information may indicate multiple or all of the multiple slice types supported by the second TA (the first slice is one of them).
- the second TA may be TA#5, and TA#5 supports slice #1 and slice #2 among the rejected slices.
- the first indication information may indicate that TA#5 supports slice #1 and slice #2.
- the advantage of the above setting is that since the amount of information in the first indication information becomes larger, the terminal device can learn that multiple rejected slices can be available in the second TA according to the first indication information. In this way, after moving to the second TA, the terminal device If the device wants to use at least one of the multiple rejected slices for communication, it can initiate a registration request again to request access to the corresponding slice.
- This can increase the number or types of network slices that terminal devices can use within the current wireless network coverage to a greater extent, meet the needs of terminal devices for communication by using network slices to a greater extent, and further improve user experience.
- the first indication information includes support information of multiple TAs for the rejected slices, each of the multiple TAs belongs to the first RA and supports at least one of the rejected slices, and the second TA is multiple any one of the TAs.
- the first indication information has a larger amount of information and can simultaneously indicate the support of the rejected slices by multiple TAs.
- one TA supports a specific slice or slices
- another TA supports a specific slice or slices. slice.
- the terminal device After the terminal device moves to one of the TAs and determines that it needs to access one or more rejected slices supported by the TA based on actual needs, it can initiate a second registration request message to request access to the corresponding slices.
- the above settings greatly increase the probability and frequency of sending the second registration request message, that is, the probability and frequency of sending access requests to the rejected slices are also greatly increased, thereby increasing the terminal device's ability to operate in the current wireless network to a greater extent.
- the number or type of network slices that can be used within the coverage area can meet the needs of terminal devices for communication through the use of network slices to a greater extent, further improving user experience.
- the first indication information is also used to indicate that the third TA supports the second slice, the third TA belongs to the first RA, the second slice is one of the rejected slices, and the second slice and the first slice may be the same. Can be different.
- the second TA can be TA#2, which only supports slice #1 among the rejected slices, Then the first slice at this time is slice #1.
- the third TA may be TA#5, and TA#5 supports slice #1 and slice #2 among the rejected slices. In this case, the second slice may be slice #1 or slice #2.
- the first indication information may indicate multiple or all of the multiple slices supported by the third TA (the second slice being one of them).
- the first indication information includes support information of multiple TAs for the rejected slices, and the multiple TAs are all TAs in the first RA that support at least one slice among the rejected slices.
- the first indication information includes the support information of these three TA pairs for the rejected slice. . That is, the first indication information may simultaneously indicate which slice or slices the three TAs support.
- the first indication information includes support information of multiple TAs for the rejected slices, and the support information is used to indicate that each TA of the multiple TAs supports at least one slice of the rejected slices, or for Indicates a slice of the rejected slices supported by each of a plurality of TAs, each of the plurality of TAs belonging to the first RA, the plurality of TAs including the second TA.
- the support information may include identifiers of multiple TAs and identifiers of multiple rejected slices.
- the multiple TA identifiers have a mapping (corresponding) relationship with the identifiers of multiple slices. According to the support information, it can or where Which rejected slices are supported by each TA, and which TAs support each of these slices.
- the first indication information may exist in the form of a mapping table, which includes a one-to-one correspondence between multiple specific TAs and rejected slices, and the mapping table is sent according to a certain timing.
- a mapping table which includes a one-to-one correspondence between multiple specific TAs and rejected slices, and the mapping table is sent according to a certain timing.
- TA#2 slice #1; TA#3: slice #2; TA#5: slice #1, slice #2; TA is used as the index at this time. or:
- step 504 before the terminal device receives the registration acceptance message from the AMF, that is, before the AMF sends the registration acceptance message to the terminal device, the method 500 also includes:
- the terminal device sends first capability indication information to the core network device, and the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the AMF sends the registration acceptance message to the terminal device according to the first capability indication information.
- the method 500 stipulates that the terminal device sends the first capability indication information to the AMF in advance to indicate whether it has the ability to receive the first indication information.
- the registration acceptance message sent by the AMF to the terminal device carries the first indication information.
- the first capability indication information may be explicitly (directly) indicated, for example, in accordance with protocol or system regulations, as a string of specific codes, or a bit of 0 or 1, or distinguished by NULL and non-NULL.
- the first capability indication information may also be an implicit (indirect) indication, which is not limited in this application.
- the first capability indication information may include a bit of 1 to indicate that the terminal device has the ability to receive the first indication information, and a bit of 0 to indicate that the terminal device does not have the ability to receive the first indication information.
- the first capability indication information may be carried in the first registration request message.
- the first capability indication information may also be carried through other messages in the prior art, or the terminal device may separately send the first capability indication information to the AMF, which is not limited in this application.
- the AMF can also query the capability information of the terminal device from other core network elements (such as NSSF), and determine whether the terminal device has the ability to receive the first indication information based on the capability information. . At this time, the action of the terminal device sending the first capability indication information to the AMF can be omitted.
- NSSF core network elements
- FIG. 6 is a schematic flow chart of the communication method 600 provided by the embodiment of the present application.
- the embodiment shown in FIG. 6 can be regarded as a modification of the embodiment shown in FIG. 5 .
- the communication method 600 provided by the embodiment of the present application is described below with reference to Figure 6.
- the method 600 includes:
- Step 601 The terminal device sends a first registration request message to the AMF in the first tracking area TA, where the first registration request message carries the requested slice.
- step 601 the AMF receives the first registration request message from the terminal device.
- the first registration request message may also carry first capability indication information, and the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the AMF may send a registration acceptance message to the terminal device according to the first capability indication information.
- Step 602 AMF determines allowed slices and rejected slices.
- Step 603 AMF allocates the first registration area RA as the current RA of the terminal device according to the allowed slice.
- Step 604 The AMF sends a registration acceptance message to the terminal device.
- the registration acceptance message includes information about allowed slices, information about rejected slices, information about the first RA, and first indication information.
- the terminal device receives the registration acceptance message from the AMF.
- Step 605 The terminal device continues other registration processes to complete the registration.
- Step 606 When the terminal device moves from the first TA to the second TA, the terminal device sends a second registration request message to the AMF according to the first indication information.
- the second registration request message includes the information (eg, identification) of the first slice.
- the AMF receives the second registration request message from the terminal device.
- steps 601-606 can be understood with reference to steps 501-506 in the method 500, and only the differences will be described here.
- the main difference from the aforementioned embodiment shown in Figure 5 is that the content indicated by the first indication information in method 600 and method 500 is different, causing the terminal device to send a second registration request message to the AMF.
- the success rate of requesting access to the first slice also varies.
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices in the second TA, and the second TA belongs to the first RA and supports the rejected slices. At least one slice in , the rejected slices include the first slice.
- the registration acceptance message also carries a first indication message.
- the first indication message only indicates to the terminal device that the second TA may support one or more of the rejected slices, but does not Clearly indicate which one or which ones it supports.
- the terminal device triggers the registration process on its own and sends the registration request message to the AMF again (i.e., the second registration request message).
- the requested slice carried in the second registration request message includes the first slice, and after obtaining approval from the AMF, the terminal device can access the first slice for communication.
- the above settings can expand the number or types of network slices that the terminal device can use within the current wireless network coverage, and also increase the types of PDU sessions that the terminal device can establish, satisfying the needs of the terminal device through use to a greater extent. network slicing for communication needs, thereby improving user experience test.
- the method 600 provided in this embodiment will not open the second TA's support information for the rejected slices, which can ensure that the operator's slice deployment information will not be opened to the terminal device, which has higher security. performance.
- the terminal device initiates a connection request to the first slice through the second registration request message in the second TA, it may be rejected because the second TA does not support the first slice.
- the first TA is TA#1 in Table 2
- the second TA is TA#2
- TA#2 supports slice #1 among the rejected slices.
- the terminal device moves from TA#1 to TA#2 and determines that it needs to access slice #1 (that is, the first slice is slice #1), it can initiate a registration request again at this time to request access to slice #. 1. Since the first slice (slice #1) requested by the terminal device is a slice supported by the second TA, the AMF may allow the terminal device to access the first slice.
- the first TA is TA#1 in Table 2
- the second TA is TA#2
- TA#2 supports slice #1 among the rejected slices.
- the terminal device moves from TA#1 to TA#2 and determines that it needs to access slice #2 (that is, the first slice is slice #2), it can initiate a registration request again at this time to request access to slice #. 2. Since the first slice (slice #2) requested by the terminal device is not supported by the second TA, the AMF may deny the terminal device access to the first slice.
- the first indication information may be carried in the registration accept message as an independent information element.
- the first indication information may include the identity of the second TA, such as TAI or TAC.
- the second TA may be any one of multiple TAs within the first RA that supports at least one of the rejected slices.
- the second TA may be any one of TA#2, TA#3, and TA#5.
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices within a TA set or any TA in the list (list).
- Each TA supports at least one slice in the rejected slices, and the second TA is any one in the TA set.
- the first indication information may indicate that the terminal device is allowed to initiate a connection request to any of the rejected slices in each TA of the plurality of TAs.
- Each TA of the plurality of TAs supports at least one of the rejected slices.
- the first indication information may include identities of the multiple TAs.
- the TA set may include TA#2, TA#3 and TA#5. of several or all.
- the first indication information may indicate that the terminal device can initiate a connection request for any one of the rejected slices in TA#2 and TA#3 (in this case, the TA set includes TA#2 and TA#3).
- the first indication information may include identification information of TA#2 and TA#3.
- the terminal device can initiate a connection request to any of the rejected slices in any TA it moves to, thereby increasing the frequency of sending the second registration message and increasing the number of connections to a greater extent.
- the number or type of network slices that a terminal device can use within the current wireless network coverage can meet the needs of the terminal device for communication by using network slices to a greater extent and further improve the user experience.
- the first indication information includes a TA set
- the TA set includes identifications of TAs that allow the terminal device to initiate a connection request to any one of the rejected slices
- the TA set includes the second TA identification.
- the TA set may be all TAs within the first RA that support at least one of the rejected slices.
- the TA set may include TA#2, TA#3 and TA#5 in Table 2.
- the AMF may first determine the TA set, for example, put the TAs of at least one slice in the first RA that support rejection into the set. For example, it is determined that the second TA belongs to the first RA and supports at least one of the rejected slices, so the second TA can be placed within the set.
- FIG. 7 is a schematic flow chart of the communication method 700 provided by the embodiment of the present application.
- the embodiment shown in FIG. 7 can be regarded as a modification of the embodiment shown in FIG. 5 .
- the communication method 700 provided by the embodiment of the present application is described below with reference to Figure 7.
- the method 700 includes:
- Step 701 The terminal device sends a first registration request message to the AMF in the first tracking area TA.
- the first registration request message carries the requested slice.
- step 701 the AMF receives the first registration request message from the terminal device.
- the first registration request message may also carry first capability indication information, and the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the AMF may send a registration acceptance message to the terminal device according to the first capability indication information.
- Step 702 AMF determines allowed slices and rejected slices.
- Step 703 AMF allocates the first registration area RA as the current RA of the terminal device according to the allowed slice.
- Step 704 The AMF sends a registration acceptance message to the terminal device.
- the registration acceptance message includes allowed slice information, rejected slice information, first RA information, and first indication information.
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first network slice access stratum group (NSASG), the first slice belongs to the rejected slice, and the first RA Including the second TA.
- NSASG network slice access stratum group
- the terminal device receives the registration acceptance message from the AMF.
- Step 705 The terminal device continues other registration processes to complete the registration.
- Step 707 The terminal device receives the information of the first NSASG through the broadcast message of the second TA.
- Step 706 The terminal device camps on the second TA, and sends a second registration request message to the AMF according to the first indication information, where the second registration request message includes the first slice.
- the AMF receives the second registration request message from the terminal device.
- the above steps 701-706 can be understood with reference to steps 501-506 in the method 500, and only the differences are described here.
- the main difference from the aforementioned embodiment shown in Figure 5 lies in that the content or form indicated by the first indication information in method 700 and method 500 are different.
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first NSASG.
- multiple slices can be mapped into one NSASG, and then the information of the NSASG will be carried in the message broadcast on the RAN air interface.
- the terminal device can monitor the NSASG corresponding to the current cell or TA through the air interface.
- NSASG is based on cells or TAs. Since each cell can only belong to one TA, the relationship between NSASG and TA can be many-to-one or one-to-one.
- the terminal device can query the core network, or the core network can configure the corresponding relationship between NSASG and slices. For example, NSASG#1 corresponds to slice #1 and slice #2, then the cell or TA broadcasting NSASG1 should support slice #1 and slice #2. However, the corresponding relationship needs to be configured and updated by the core network, and the terminal device cannot learn the corresponding relationship from the broadcast information.
- the AMF sends first indication information to the terminal device, the first indication information is used to indicate the There is a mapping relationship between all slices and the first NSASG, which indicates that the TA corresponding to the first NSASG supports the first slice. And the first slice belongs to the rejected slice, the first RA includes the second TA.
- the first slice may not belong to the rejected slices.
- the second TA may not belong to the first RA.
- the terminal device receives the information of the first NSASG through the broadcast message of the second TA of the first RA.
- the information of the first NSASG may be carried in a system information block (for example, system information block 1 ( system information block 1, SIB1)).
- the terminal device receives the information of the first NSASG, and can determine according to the first indication information that the second TA corresponding to the information of the first NSASG (that is, the TA that sends the information of the first NSASG) can support the first slice. Therefore, the terminal device can be camped in the second TA (for example, in a certain cell in the second TA), and send a second registration request message to the AMF, where the second registration request message includes the information of the first slice. After obtaining approval from the AMF, the terminal device can access the first slice for communication.
- the registration acceptance message also carries a first indication message.
- the terminal device can know in which NSASG corresponding TA a specific rejected slice is available. , for example, according to the first indication information, the terminal can know that the rejected first slice is actually available in the second TA corresponding to the first NSASG, when the terminal device receives the information of the first NSASG through the broadcast message of the second TA. At this time, the terminal can learn that the second TA can support the first slice.
- the terminal device can reside in the second TA, and Initiate a registration request again to request access to the first slice.
- the above settings can expand the number or types of network slices that the terminal device can use within the current wireless network coverage, and also increase the types of PDU sessions that the terminal device can establish, satisfying the needs of the terminal device through use to a greater extent. Network slicing is required for communication, thereby improving user experience.
- method 700 does not open the specific TA's slice deployment situation to the terminal device. It only provides the mapping relationship between NSASG and rejected slices. When NSASG broadcast information is detected, a request for the rejected slice can be triggered without switching to The corresponding TA is triggered again. For example, it can only be located at the edge of the TA at this time, which is more flexible and applicable to more scenarios.
- the first indication information includes the identity of the first slice and the identity of the first NSASG.
- the first indication information may be used to indicate that there is a mapping relationship between the first slice and multiple NSASGs including the first NSASG, that is, indicating that the first slice corresponds to multiple NSASGs, and the first NSASG may be Any one of the multiple NSASG species.
- the terminal device can reside in the corresponding TA and initiate a registration request again, requesting access to the first slice.
- the first indication information may be used to indicate that there is a mapping relationship between multiple slices including the first slice and the first NSASG, that is, indicating that the multiple slices correspond to the first NSASG and indicating the TA corresponding to the first NSASG.
- the first slice can be any one of the plurality of slice types.
- the first indication information is used to indicate a mapping relationship between multiple slices (for example, all) of the rejected slices and NSASG, and the first slice is any one of the multiple slices.
- the probability and frequency of sending the second registration request message are greatly increased, that is, the probability and frequency of sending access requests to the rejected slices are also greatly increased, which can greatly increase the terminal device's current wireless connection.
- the number or type of network slices that can be used within the network coverage area can satisfy terminal equipment to a greater extent. Prepare for the need for communication by using network slicing to further improve user experience.
- the first indication information may exist in the form of a mapping table, which includes correspondences between multiple specific slices and multiple NSASGs, and the mapping table is sent according to a certain timing, for example :NSASG#1: Slice#1, Slice#2 or Slice#1:NSASG#1, NSASG#2, etc.
- step 704 before the terminal device receives the registration acceptance message from the AMF, that is, before the AMF sends the registration acceptance message to the terminal device, the method 700 also includes:
- the terminal device sends second capability indication information to the core network device.
- the second capability indication information is used to indicate that the terminal device has the ability to receive NSASG information.
- the AMF sends the registration acceptance message to the terminal device according to the second capability indication information.
- the method 700 provided by the embodiment of this application stipulates that the terminal device sends second capability indication information to the AMF in advance to indicate whether it has the ability to receive NSASG information.
- the registration acceptance message sent by the AMF to the terminal device carries the first indication information.
- the first capability indication information may be explicitly (directly) indicated, for example, in accordance with the provisions of the protocol or system, as a string of specific codes, or a bit of 0 or 1, or distinguished by NULL and non-NULL.
- the second capability indication information may also be an implicit (indirect) indication, which is not limited in this application.
- the second capability indication information may include a bit of 1 to indicate that the terminal device has the ability to receive NSASG information, and a bit of 0 to indicate that the terminal device does not have the ability to receive NSASG information.
- the second capability indication information may be carried in the first registration request message.
- the second capability indication information can also be carried through other messages in the existing technology, or the terminal device can send the second capability indication information to the AMF alone, or combine the first capability indication information and the second capability indication information. Integrate and package them together and send them to AMF. This application is not limited to this.
- the AMF can also query the capability information of the terminal device from other core network elements (such as NSSF), and determine whether the terminal device has the ability to receive the second indication information based on the capability information. . At this time, the action of the terminal device sending the second capability indication information to the AMF can be omitted.
- NSSF core network elements
- FIG. 8 is a schematic flow chart of the communication method 800 provided by the embodiment of the present application.
- the embodiment shown in FIG. 8 can be regarded as a modification of the embodiment shown in FIG. 5 .
- the communication method 800 provided by the embodiment of the present application is described below with reference to Figure 8.
- the method 800 includes:
- Step 801 The terminal device sends a first registration request message to the AMF in the first tracking area TA, where the first registration request message carries the requested slice.
- step 801 the AMF receives the first registration request message from the terminal device.
- the first registration request message may also carry first capability indication information, and the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the AMF may send a registration acceptance message to the terminal device according to the first capability indication information.
- Step 802 AMF determines allowed slices and rejected slices.
- Step 803 AMF allocates the first registration area RA as the current RA of the terminal device according to the allowed slice.
- Step 804 The AMF sends a registration acceptance message to the terminal device.
- the registration acceptance message includes information about allowed slices, information about rejected slices, information about the first RA, and first indication information.
- the first indication information is used to indicate the second TA.
- the first slice is supported, the second TA belongs to one of the first RAs, and the first slice belongs to one of the rejected slices.
- the terminal device receives the registration acceptance message from the AMF.
- Step 805 The terminal device continues other registration processes to complete the registration.
- the terminal device when the terminal device moves from the first TA to the second TA, the terminal device sends a message to the AMF according to the first instruction information.
- the second registration request message includes the first slice.
- the terminal device directly initiates a session establishment request and skips the registration process.
- method 800 also includes:
- Step 806 According to the first instruction information, when the terminal device is located in the second TA area that supports the first slice, if it still needs to access the first slice (which can be determined according to the needs of the APP, etc.), initiate In the session establishment request, add the first slice supported by the first TA to the session establishment request. AMF does not reject the session establishment request of the terminal device and performs the session establishment process based on the current TA of the terminal device and the slicing conditions supported by the TA.
- Step 807 The terminal device triggers a change in TA due to handover.
- Step 808a The terminal device enters the idle (IDLE) state and initiates a service request (service request) due to receiving a paging message (paging all TAs in the first RA), or enters step 808b.
- Step 808b The terminal device initiates a service request due to business needs, which carries session information that needs to be activated, etc.
- Step 809 The AMF discovers that the terminal device triggers a TA change due to the switching process in step 807, or verifies the current TA of the terminal device and the slicing information of the terminal device session after receiving a service request from the terminal. If there is a session whose slices are not supported in the current TA, the release process of the session is triggered.
- Step 810 Perform the PDU session release process.
- FIG. 9 is a schematic flow chart of the communication method 900 provided by the embodiment of the present application.
- the embodiment shown in FIG. 9 can be regarded as a modification of the embodiment shown in FIG. 5 .
- the communication method 900 provided by the embodiment of the present application is described below with reference to Figure 9.
- the method 900 includes:
- Step 901 The terminal device sends a first registration request message to the AMF in the first tracking area TA.
- the first registration request message carries information about the requested slice and first capability indication information, where the first capability indication information is used to indicate to the terminal Whether the device has the ability to receive the first indication information in any of the aforementioned embodiments.
- Step 902 AMF determines allowed slices and rejected slices.
- Step 903 The AMF allocates the first RA or the second RA to the terminal device according to the allowed slices and the indication of the first capability indication information.
- the AMF may allocate the first RA to the terminal device according to the method in the aforementioned steps 503, 603, and 703. At least one TA of is able to support at least one of the rejected slices.
- the AMF allocates a second RA to the terminal device, and any TA of the second RA type may not support the rejected slice.
- Table 3 uses Table 3 as an example for explanation.
- AMF determines that the allowed slices only include slice #3, and the rejected slices include slice #1 and slice #2. If the first capability indication information indicates that the terminal device has the ability to receive the first indication information, the first RA is assigned to the terminal device according to the method introduced in the previous embodiment (see the introduction of step 503 for details). This is the first RA including five TAs from TA#1 to TA#5. If the first capability indication information indicates that the terminal device does not have the ability to receive the first indication information, the terminal device is assigned a second RA. In addition to supporting slice #3, each TA in the second RA should also Neither of the rejected slices is supported, that is, slice #1 and slice #2 cannot be supported. Therefore, compared with the first RA, TA#2, TA#3, and TA#5 should be excluded in the second RA, that is, the second RA only includes TA#1 and TA#4.
- step 904a is entered.
- the AMF can also obtain the first capability indication information through other methods.
- the first capability indication information can be obtained through the subscription information of the terminal device.
- the AMF itself can store the subscription information, or the AMF can also obtain the first capability indication information through
- the contract information (first capability indication information) is obtained from other network elements such as NSSF and UDM. This application does not specifically limit the method by which the AMF obtains the first capability indication information.
- the AMF sends a registration acceptance message to the terminal device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is used to indicate that the second tracking area TA supports The first slice, the second TA belongs to the first RA, and the first slice belongs to the rejected slice; or,
- the first indication information is used to instruct the terminal device to allow initiating a connection request for any one of the rejected slices in the second TA.
- the second TA belongs to the first RA and supports at least one of the rejected slices.
- the rejected slice Include the first slice; or,
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first network slice access layer group NSASG, the first slice belongs to the rejected slice, and the first RA includes the second TA.
- the terminal device When the terminal device receives the registration acceptance message containing the first indication information, it may continue to follow the relevant steps in the aforementioned methods 500 to 800 to send a second registration request message to the AMF.
- the second registration request message includes the first slice. Information.
- step 904b is entered.
- the AMF sends a registration acceptance message to the terminal device.
- the registration acceptance message includes information about the rejected slice and information about the second RA. None of the TAs in the second RA supports the rejected slice.
- the terminal device receives the registration acceptance message that does not contain the first indication information and the terminal device moves to the second TA, since the second TA does not belong to the current RA, it may be that the terminal device moves to the original RA.
- mobility registration updates are caused, so a new registration needs to be initiated to the core network again. registration process.
- FIGS. 10 to 13 The communication method of the embodiment of the present application is described in detail above with reference to FIGS. 1 to 9 .
- the device of the embodiment of the present application is described in detail with reference to FIGS. 10 to 13 . It should be understood that the device shown in FIGS. 10 to 13 can implement one or more steps in the method flow shown in FIGS. 5 to 9 . To avoid repetition, they will not be described in detail here.
- FIG 10 is a schematic block diagram of a terminal device 1000 provided by an embodiment of the present application. As shown in Figure 10, the terminal device 1000 includes: a sending module 1010 and a receiving module 1020.
- the sending module 1010 is configured to send a first registration request message to the core network device when the terminal device 1000 is within the first tracking area TA;
- the receiving module 1020 is configured to receive a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is Instructing the second TA to support the first slice, the second TA belonging to the first RA, and the first slice belonging to the rejected slice;
- the sending module 1010 is also configured to send a second registration request message to the core network device according to the first indication information when the terminal device 1000 moves from the first TA to the second TA,
- the second registration request message includes the first slice.
- the first indication information includes the identifier of the second TA and the identifier of the first slice.
- the first indication information includes support information of multiple TAs for the rejected slice, and each of the multiple TAs belongs to the first RA and supports the rejected slice. At least one slice, the second TA is any one of the plurality of TAs.
- the sending module is further configured to send first capability indication information to the core network device, where the first capability indication information is Instructing that the terminal device has the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- the sending module 1010 is configured to send a first registration request message to the core network device when the terminal device 1000 is in the first tracking area TA;
- the receiving module 1020 is configured to receive a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is Instructing the terminal device 1000 to allow initiation of a connection request to any one of the rejected slices in a second TA that belongs to the first RA and supports at least one of the rejected slices. a slice, the rejected slice including the first slice;
- the sending module 1010 is also configured to, when the terminal device 1000 moves from the first TA to the second TA, send a second registration request message to the core network device according to the first indication information,
- the second registration request message includes the first slice.
- the first indication information includes the identification of the second TA.
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices in any TA in the TA set.
- Each TA supports at least one slice in the rejected slices, and the second TA is any one in the TA set.
- the sending Module before the receiving module receives the registration acceptance message from the core network device, the sending Module, further configured to send first capability indication information to the core network device, where the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- Sending module 1010 configured to send a first registration request message to the core network device when the terminal device 1000 is within the first tracking area TA;
- the receiving module 1020 is configured to receive a registration acceptance message from the core network device.
- the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information.
- the first indication information is There is a mapping relationship between indicating a first slice and a first network slice access layer group NSASG, the first slice belongs to the rejected slice, and the first RA includes a second TA;
- the receiving module 1020 is also configured to receive the information of the first NSASG through the broadcast message of the second TA;
- the sending module 1010 is also configured to send a second registration request message to the core network device when the terminal device resides on the second TA according to the first indication information.
- the second registration request message The message includes the first slice.
- the first indication information includes the identifier of the first slice and the identifier of the first NSASG.
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is any one of the multiple slices.
- the sending module is further configured to send first capability indication information to the core network device, where the first capability indication information is Instructing that the terminal device has the ability to receive the first indication information.
- the first capability indication information is carried in the first registration request message.
- the above-mentioned terminal device 1000 can be the terminal device 1100 in the figure below, in which the functions of the sending module 1010 and the receiving module 1020 can be implemented through the transceiver 1101 of the terminal device (ie, the control circuit and the antenna together) .
- the structure of the terminal device 1100 according to the embodiment of the present application will be introduced below with reference to FIG. 11 .
- FIG. 11 is a schematic structural diagram of a terminal device 1100 according to an embodiment of the present application.
- the terminal device 1100 may be adapted to the system shown in FIG. 1 to perform the functions of the terminal device (UE) in the above method embodiment.
- FIG. 11 shows only the main components of the terminal device.
- the terminal device 1100 includes a processor 1102, a memory, a control circuit, an antenna, and an input and output device.
- the processor 1102 is mainly used to process communication protocols and communication data, control the entire terminal device, execute software programs, and process data of the software programs, for example, to support the terminal device to perform the actions described in the above method embodiments.
- Memory is mainly used to store software programs and data.
- the control circuit is mainly used for conversion of baseband signals and radio frequency signals and processing of radio frequency signals.
- the control circuit and the antenna together can also be called the transceiver 1101, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
- Input and output devices such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users.
- the processor 1102 can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program.
- the processor 1102 performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit.
- the radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal out in the form of electromagnetic waves through the antenna.
- the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor.
- the processor converts the baseband signal into data and processes the data.
- FIG. 11 only shows one memory and one processor. In an actual terminal device, there may be multiple processors and multiple memories.
- the memory may also be called a storage medium or a storage device, which is not limited in the embodiments of the present application.
- the processor may include a baseband processor and a central processor.
- the baseband processor is mainly used to process communication protocols and communication data.
- the central processor is mainly used to control and execute the entire terminal device.
- the software program processes the data of the software program.
- the processor in Figure 11 can integrate the functions of the baseband processor and the central processing unit.
- the baseband processor and the central processing unit can also be independent processors, interconnected through technologies such as buses.
- the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capabilities, and various components of the terminal device may be connected through various buses.
- the baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip.
- the central processing unit can also be expressed as a central processing circuit or a central processing chip.
- the function of processing communication protocols and communication data can be built into the processor, or can be stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.
- FIG 12 is a schematic block diagram of the core network device 1200 provided by the embodiment of the present application.
- the core network device 1200 shown in Figure 12 includes a receiving module 1210 and a sending module 1220.
- the receiving module 1210 is used to receive the first registration request message from the terminal device
- Sending module 1220 configured to send a registration acceptance message to the terminal device, where the registration acceptance message includes information about the rejected slice, information about the first registration area RA, and first indication information,
- the first indication information is used to indicate that the second TA supports the first slice, the second TA belongs to the first RA, and the first slice belongs to the rejected slice; or,
- the first indication information is used to instruct the terminal device to allow initiating a connection request for any one of the rejected slices in the second TA, which belongs to the first RA and supports the at least one of the rejected slices, the rejected slices including the first slice; or,
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first network slice access layer group NSASG, the first slice belongs to the rejected slice, and the first RA includes the Two TA;
- the receiving module 1210 is also configured to receive a second registration request message from the terminal device, where the second registration request message includes the first slice.
- the first indication information includes the identity of the second TA and the identity of the first slice; or the first indication information includes the identity of the second TA; or the first indication information includes the identity of the second TA.
- An indication information includes the identifier of the first slice and the identifier of the first NSASG.
- the first indication information includes support information of multiple TAs for the rejected slices, and each of the multiple TAs belongs to the first RA and supports at least one of the rejected slices.
- slice, the second TA is any one of the plurality of TAs; or,
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices in any TA in the TA set, and each TA in the TA set is allowed to initiate a connection request to any slice in the rejected slice.
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is any one of the multiple slices.
- the receiving module 1210 is further configured to receive first capability indication information from the terminal device, where the first capability indication information is used to indicate that the terminal device has the ability to receive the first indication information. ;
- the sending module 1220 is specifically configured to send the registration acceptance message to the terminal device according to the first capability indication information.
- the first capability indication information is carried in the first registration request message.
- the receiving module 1210 is configured to receive a first registration request message from a terminal device, where the first registration request message includes first capability indication information, and the first capability indication information is used to indicate whether the terminal device is capable of receiving the first the ability to indicate information;
- Sending module 1220 when the first capability indication information indicates that the terminal device has the ability to receive the first indication information, is configured to send a registration acceptance message to the terminal device, where the registration acceptance message includes information about the rejected slices. , information of the first registration area RA and first indication information, the first indication information is used to indicate that the second tracking area TA supports the first slice, the second TA belongs to the first RA, and the first The slice belongs to the rejected slice; or,
- the first indication information is used to instruct the terminal device to allow initiating a connection request for any one of the rejected slices in the second TA, which belongs to the first RA and supports the at least one of the rejected slices, the rejected slices including the first slice; or,
- the first indication information is used to indicate that there is a mapping relationship between the first slice and the first network slice access layer group NSASG, the first slice belongs to the rejected slice, and the first RA includes the Two TA;
- the sending module is configured to send a registration acceptance message to the terminal device, where the registration acceptance message includes the rejected slice. information and the information of the second RA. None of the TAs in the second RA supports the rejected slice.
- the first indication information includes the identity of the second TA and the identity of the first slice; or the first indication information includes the identity of the second TA; or the first indication information includes the identity of the second TA.
- An indication information includes the identifier of the first slice and the identifier of the first NSASG.
- the first indication information includes support information of multiple TAs for the rejected slices, each of the multiple TAs belongs to the first RA and supports at least one slice of the rejected slices,
- the second TA is any one of the plurality of TAs; or,
- the first indication information is used to indicate that the terminal device is allowed to initiate a connection request for any one of the rejected slices in any TA in the TA set, and each TA in the TA set is allowed to initiate a connection request to any slice in the rejected slice.
- the first indication information is used to indicate the mapping relationship between multiple slices in the rejected slices and NSASG, and the first slice is any one of the multiple slices.
- Figure 13 is a schematic structural diagram of the core network device 1300 provided by the embodiment of the present application.
- the core The heart network device 1300 includes: a processor 1310, a memory 1320, and a communication interface 1330.
- the memory 1320 stores instructions, and the processor 1310 is used to execute the instructions in the memory 1320.
- the processor 1310 is used to execute the method provided by any of the above method embodiments.
- the processor 1310 also uses Communicate with the outside world through the control communication interface 1330.
- processor 1310 the memory 1320 and the communication interface 1330 can communicate with each other through internal connection paths to transfer control and/or data signals.
- the memory 1320 can be integrated in the processor 1310 or can be provided separately from the processor 1310 .
- the core network device 1300 can be used to perform various steps in the communication methods in Figures 5-9.
- the core network device 1300 can include various modules in Figure 12 for performing the foregoing communication methods.
- each module in the core network device 1300 and the above-mentioned other operations and/or functions are respectively intended to implement the corresponding processes of the communication methods in Figures 5-9.
- the specific process of each module performing the above corresponding steps has been described in detail in the method. For the sake of brevity, it will not be described again here.
- the processor in the embodiment of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), or special-purpose integrated processors.
- Circuit application specific integrated circuit, ASIC
- off-the-shelf programmable gate array field programmable gate array, FPGA
- a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
- non-volatile memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
- non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory.
- Volatile memory can be random access memory (RAM), which is used as an external cache.
- RAM random access memory
- static random access memory static random access memory
- DRAM dynamic random access memory
- RAM synchronous dynamic random access memory
- SDRAM synchronous dynamic random access memory
- double data rate SDRAM double data rate SDRAM
- DDR SDRAM double data rate SDRAM
- enhanced SDRAM enhanced synchronous dynamic random access memory
- SLDRAM synchronous connection dynamic random access memory access memory
- direct rambus RAM direct rambus RAM, DR RAM
- the present application also provides a computer program product.
- the computer program product includes: computer program code.
- the computer program code When the computer program code is run on a computer, it causes the computer to execute the steps shown in Figures 5 to 9. The method of any one of the embodiments is shown.
- the present application also provides a computer-readable medium.
- the computer-readable medium stores program code.
- the program code When the program code is run on a computer, it causes the computer to execute the steps shown in Figures 5-9. The method of any one of the embodiments is shown.
- this application also provides a system, which includes the aforementioned one or more terminal devices, one or more access network devices, and one or more core network devices.
- the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any other combination.
- the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
- the computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
- the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
- the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmit to another website, computer, server or data center through wired (such as infrared, wireless, microwave, etc.) means.
- the computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server or a data center that contains one or more sets of available media.
- the usable media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media.
- the semiconductor medium may be a solid state drive.
- "instruction” may include direct instruction and indirect instruction, and may also include explicit instruction and implicit instruction.
- the information indicated by a certain piece of information (such as the "instruction information” mentioned above) is called the information to be indicated.
- the information to be indicated can be directly indicated.
- Indication information such as the information to be indicated itself or the index of the information to be indicated, etc.
- the information to be indicated may also be indirectly indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance.
- the indication of specific information can also be achieved by means of a pre-agreed (for example, protocol stipulated) arrangement order of each piece of information, thereby reducing the indication overhead to a certain extent.
- the "communication protocol” involved in the embodiment of this application may refer to a standard protocol in the communication field, and may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.
- At least one refers to one or more, and “plurality” refers to two or more.
- At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
- at least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
- the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
- the execution order of each process should be determined by its functions and internal logic, and should not be determined by the implementation process of the embodiments of the present application. constitute any limitation.
- the disclosed systems, devices and methods can be implemented in other ways.
- the device embodiments described above are only illustrative.
- the division of the units is only a logical function division. In actual implementation, there may be other division methods.
- multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
- the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
- 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 they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
- each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
- 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.
- the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
- the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请提供了一种通信方法及终端设备、核心网设备,其中方法包括:终端设备在第一TA内向核心网设备发送第一注册请求消息;终端设备接收来自核心网设备的注册接受消息,注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,第一指示信息用于指示第二TA支持第一切片,第二TA属于第一RA,第一切片属于拒绝的切片;当终端设备从第一TA移动至第二TA时,终端设备根据第一指示信息向核心网设备发送第二注册请求消息,第二注册请求消息包括第一切片的信息。本申请能够更好地满足终端设备通过使用网络切片进行通信的需求。
Description
本申请要求于2022年03月28日提交国家知识产权局、申请号为202210329805.5、申请名称为“通信方法及终端设备、核心网设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信技术领域,尤其涉及一种通信方法及终端设备、核心网设备。
第五代(5th Generation,5G)通信系统引入了网络切片的概念,网络切片技术能够实现将一个物理网络划分为多个虚拟网络。一个虚拟网络当作一个“网络切片”,每个网络切片之间是相互独立的。一个终端设备中的不同会话可能需要与各个会话相对应的网络切片来提供服务。
在实际应用中,终端设备在请求注册到网络时携带请求的网络切片,并在成功注册到网络之后,从网络侧获得允许的网络切片和注册区域,在该注册区域内的任一跟踪区域终端设备均可以接入到允许的网络切片,并使用该允许的网络切片提供的服务。然而,对于请求的网络切片中未被包含在允许的网络切片中的其他切片(即拒绝的网络切片),在当前的注册区域内,终端设备即使处在支持该拒绝的网络切片的跟踪区域内时,终端设备也不被允许使用该拒绝的网络切片。因此,大大限定了终端设备在当前的网络覆盖范围内可以使用的网络切片的数量或类型,也限定了终端设备所能建立的PDU会话的类型,无法满足终端设备通过使用网络切片进行通信的需求。
在这种情形下,如何更好地满足终端设备通过使用网络切片进行通信的需求成为有待解决的技术问题。
发明内容
本申请实施例提供一种无线通信方法及终端设备、核心网设备,以期更好地满足终端设备通过使用网络切片进行通信的需求。
第一方面,提供了一种通信方法,包括:
终端设备在第一跟踪区域TA内向核心网设备发送第一注册请求消息;
所述终端设备接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片的信息;
当所述终端设备从所述第一TA移动至所述第二TA时,所述终端设备根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片。
当终端设备从第一TA移动至第二TA内时,并且终端设备根据当前业务需求(例
如某个APP的使用需求)确定需要接入第一切片以建立PDU会话,而根据第一指示信息的指示,终端设备能够获知当前所处的第二TA支持第一切片,由于第一切片在当前的RA(第一RA)内为拒绝使用的切片,因此终端设备自行触发注册流程,再次向AMF发送注册请求消息(即第二注册请求消息),第二注册请求消息中携带的请求的切片包括第一切片,待获得AMF的批准后,终端设备则可以接入该第一切片以进行通信。
根据本申请实施例提供的通信方法,注册接受消息中还携带有第一指示消息,根据该第一指示消息终端设备能够知道某个具体的被拒绝的切片在哪个TA中可用,例如根据该第一指示信息终端能够知道被拒绝的第一切片其实在第二TA中是可用的,这样当终端设备移动至第二TA内以后,如果仍然想使用第一切片进行网络通信(例如建立PDU会话),则可以再次发起注册请求,请求能够接入第一切片。通过以上设置能够扩大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,也增加了终端设备所能建立的PDU会话的类型,从更大程度上满足了终端设备通过使用网络切片进行通信的需求,从而提高了用户体验。
结合第一方面,在第一方面的某些实现方式中,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识。
结合第一方面,在第一方面的某些实现方式中,所述第一指示信息包括多个TA对所述拒绝的切片的支持信息,所示支持信息用于指示所述多个TA中的每一个TA支持所述拒绝的切片中的至少一个切片,或者用于指示所述多个TA中的每一个TA所支持的所述拒绝的切片中的切片,所述多个TA中的每一个TA均属于所述第一RA,所述多个TA包括所述第二TA。
以上设置的好处是,由于第一指示信息的信息量变大,终端设备能够根据第一指示信息获知多个被拒绝的切片能够在第二TA中可用,如此在移动到第二TA内以后,终端设备如果想使用该多个被拒绝的切片中的至少一个切片进行通信的情况下,即可以再次发起注册请求,请求能够接入相应的切片。由此能够更大程度的增大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,更大程度的满足终端设备通过使用网络切片进行通信的需求,进一步提高用户体验。
结合第一方面,在第一方面的某些实现方式中,所述终端设备接收来自所述核心网设备的注册接受消息之前,所述方法还包括:所述终端设备向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
考虑到终端设备执行(支持)的协议版本可能不一致,例如有的终端执行较高版本的协议,而有的终端执行较低版本的协议,有些版本的协议可能并不支持终端接收该第一指示信息。因此,为了避免出现接收错误、接收无法识别等问题,本申请实施例提供的方法还规定终端设备提前向AMF发送第一能力指示信息,以指示自身是否具备接收第一指示信息的能力。当确定终端设备具备接收第一指示信息的能力时,AMF向终端设备发送的注册接受消息中携带该第一指示信息。
可选地,该第一能力指示信息可以显性(直接)指示,例如按照协议或者系统的规定,为一串特定的代码,或者一比特的0或1,或者用NULL和非NULL区分。或
者,该第一能力指示信息也可以隐含(间接)指示,本申请对此不作限定。
例如,第一能力指示信息可以包括一比特的1来指示终端设备具备接收第一指示信息的能力,用一比特的0来指示终端设备不具备接收第一指示信息的能力。
结合第一方面,在第一方面的某些实现方式中,所述第一能力指示信息携带于所述第一注册请求消息中。
可选地,第一能力指示信息也可以通过现有技术中的其他消息进行携带,或者终端设备可以单独向AMF发送该第一能力指示信息,本申请对此并不限定。
第二方面,提供了一种通信方法,包括:终端设备在第一跟踪区域TA内向核心网设备发送第一注册请求消息;
所述终端设备接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示允许所述终端设备在第二TA内发起对所述拒绝的切片中的任意一个切片的连接请求,所述拒绝的切片包括第一切片;
当所述终端设备从所述第一TA移动至所述第二TA时,所述终端设备根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
根据本申请实施例提供的方法,注册接受消息中还携带有第一指示消息,第一指示信息仅向终端设备指示第二TA可能支持拒绝的切片中的某一个或者多个切片,而没有明确指示其支持的是具体的哪一个或者哪些。当终端设备移动至第二TA后,如果仍然想使用第一切片进行网络通信(例如建立PDU会话),终端设备自行触发注册流程,再次向AMF发送注册请求消息(即第二注册请求消息),第二注册请求消息中携带的请求的切片包括第一切片,待获得AMF的批准后,终端设备则可以接入该第一切片以进行通信。通过以上设置能够扩大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,也增加了终端设备所能建立的PDU会话的类型,从更大程度上满足了终端设备通过使用网络切片进行通信的需求,从而提高了用户体验。
此外,相对于前述实施例,本实施例提供的方法并不会开放第二TA对拒绝的切片的支持信息,可以保证不会开放运营商的切片部署信息给终端设备,具有更高的安全性能。当然,终端设备在第二TA内通过第二注册请求消息发起对第一切片的连接请求,可能会因为第二TA不支持第一切片而被拒绝。
结合第二方面,在第二方面的某些实现方式中,所述第一指示信息包括所述第二TA的标识。
结合第二方面,在第二方面的某些实现方式中,所述第一指示信息包括TA集合,所述TA集合包括允许所述终端设备发起对所述拒绝的切片中的任意一个切片的连接请求的TA的标识,所述TA集合包括所述第二TA标识。
结合第二方面,在第二方面的某些实现方式中,所述终端设备接收来自所述核心网设备的注册接受消息之前,所述方法还包括:所述终端设备向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
结合第二方面,在第二方面的某些实现方式中,所述第一能力指示信息携带于所述第一注册请求消息中。
第三方面,提供了一种通信方法,包括:终端设备在第一跟踪区域TA内向核心网设备发送第一注册请求消息;
所述终端设备接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系;
所述终端设备通过所述第一RA的第二TA的广播消息接收到所述第一NSASG的信息;
所述终端设备驻留到所述第二TA,并且根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
根据本申请实施例提供的方法,注册接受消息中还携带有第一指示消息,根据该第一指示消息终端设备能够知道某个具体的被拒绝的切片在哪个NSASG对应的TA内是可用的,例如根据该第一指示信息终端能够知道被拒绝的第一切片其实在第一NSASG对应的第二TA中是可用的,当终端设备通过第二TA的广播消息接收到第一NSASG的信息时,终端能够获知第二TA能够支持第一切片,这时如果确定自身仍然想使用第一切片进行网络通信(例如建立PDU会话),可以将终端设备驻留于第二TA内,并且再次发起注册请求,请求能够接入第一切片。通过以上设置能够扩大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,也增加了终端设备所能建立的PDU会话的类型,从更大程度上满足了终端设备通过使用网络切片进行通信的需求,从而提高了用户体验。
此外,该方法并没有开放具体的TA的切片部署情况给终端设备,仅提供了NSASG与拒绝的切片的映射关系,检测到NSASG广播信息时就可以触发对拒绝的切片的请求,而不用切换到对应的TA再触发,例如此时可以仅位于TA的边缘,更加灵活,适用更多的场景。
结合第三方面,在第三方面的某些实现方式中,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
结合第三方面,在第三方面的某些实现方式中,所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
结合第三方面,在第三方面的某些实现方式中,所述终端设备接收来自所述核心网设备的注册接受消息之前,所述方法还包括:所述终端设备向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
结合第三方面,在第三方面的某些实现方式中,所述第一能力指示信息携带于所述第一注册请求消息中。
第四方面,提供了一种通信方法,包括:
核心网设备接收来自终端设备的第一注册请求消息;
所述核心网设备向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝
的切片的信息、第一注册区域RA的信息以及第一指示信息,
所述第一指示信息用于指示第二TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;或者,
所述第一指示信息用于指示允许所述终端设备在第二TA内发起对所述拒绝的切片中的任意一个切片的连接请求,所述拒绝的切片包括第一切片;或者,
所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系;
所述核心网设备接收来自所述终端设备的第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
结合第四方面,在第四方面的某些实现方式中,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识;或者,所述第一指示信息包括所述第二TA的标识;或者,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
结合第四方面,在第四方面的某些实现方式中,所述第一指示信息包括多个TA对拒绝的切片的支持信息,所示支持信息用于指示所述多个TA中的每一个TA支持所述拒绝的切片中的至少一个切片,或者用于指示所述多个TA中的每一个TA所支持的所述拒绝的切片中的切片,所述多个TA中的每一个TA均属于所述第一RA,所述多个TA包括所述第二TA;或者,
所述第一指示信息包括TA集合,所述TA集合包括允许所述终端设备发起对所述拒绝的切片中的任意一个切片的连接请求的TA的标识,所述TA集合包括所述第二TA的标识;或者,
所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
结合第四方面,在第四方面的某些实现方式中,所述方法还包括:所述核心网设备接收来自所述终端设备的第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力;所述核心网设备向所述终端设备发送注册接受消息包括:所述核心网设备根据所述第一能力指示信息向所述终端设备发送所述注册接受消息。
结合第四方面,在第四方面的某些实现方式中,所述第一能力指示信息携带于所述第一注册请求消息中。
结合第四方面,在第四方面的某些实现方式中,所述核心网设备向所述终端设备发送注册接受消息之前,所述方法还包括:
所述核心网设备确定所述第二TA属于所述第一RA并支持所述拒绝的切片中的至少一个切片。
第五方面,提供了一种通信方法,包括:
核心网设备接收来自终端设备的第一注册请求消息;
所述核心网设备获取第一能力指示信息,所述第一能力指示信息用于指示所述终端设备是否具备接收第一指示信息的能力;
当所述第一能力指示信息指示终端设备具备接收所述第一指示信息的能力时,所述核心网设备向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片
的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二跟踪区域TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;或者,
所述第一指示信息用于指示允许所述终端设备在第二TA内发起对所述拒绝的切片中的任意一个切片的连接请求,所述拒绝的切片包括第一切片;或者,
所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系;
当所述第一能力指示信息指示终端设备不具备接收所述第一指示信息的能力时,所述核心网设备向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息以及第二RA的信息,所述第二RA中的任意一个TA均不支持所述拒绝的切片。
结合第五方面,在第五方面的某些实现方式中,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识;或者,
所述第一指示信息包括所述第二TA的标识;或者,
所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
结合第五方面,在第五方面的某些实现方式中,所述第一指示信息包括多个TA对拒绝的切片的支持信息,所示支持信息用于指示所述多个TA中的每一个TA支持所述拒绝的切片中的至少一个切片,或者用于指示所述多个TA中的每一个TA所支持的所述拒绝的切片中的切片,所述多个TA中的每一个TA均属于所述第一RA,所述多个TA包括所述第二TA;或者,
所述第一指示信息包括TA集合,所述TA集合包括允许所述终端设备发起对所述拒绝的切片中的任意一个切片的连接请求的TA的标识,所述TA集合包括所述第二TA的标识;或者,
所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
结合第五方面,在第五方面的某些实现方式中,所述第一能力指示信息携带于第一注册请求消息中。
第六方面,提供了一种终端设备,包括:
发送模块,用于当所述终端设备在第一跟踪区域TA内时,向核心网设备发送第一注册请求消息;
接收模块,用于接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;
所述发送模块,还用于当所述终端设备从所述第一TA移动至所述第二TA时,根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
结合第六方面,在第六方面的某些实现方式中,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识。
结合第六方面,在第六方面的某些实现方式中,所述第一指示信息包括多个TA对所述拒绝的切片的支持信息,所述多个TA中的每一个TA均属于所述第一RA并支持所述拒绝的切片中的至少一个切片,所述第二TA为所述多个TA中的任意一个。
结合第六方面,在第六方面的某些实现方式中,所述接收模块接收来自所述核心网设备的注册接受消息之前,所述发送模块,还用于向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
结合第六方面,在第六方面的某些实现方式中,所述第一能力指示信息携带于所述第一注册请求消息中。
第七方面,提供了一种终端设备,包括:
发送模块,用于当所述终端设备在第一跟踪区域TA内向核心网设备发送第一注册请求消息;
接收模块,用于接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示所述终端设备在第二TA内允许发起对所述拒绝的切片中的任意一个切片的连接请求,所述第二TA属于所述第一RA并支持所述拒绝的切片中的至少一个切片,所述拒绝的切片包括第一切片;
所述发送模块还用于,当所述终端设备从所述第一TA移动至所述第二TA时,根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
结合第七方面,在第七方面的某些实现方式中,所述第一指示信息包括所述第二TA的标识。
结合第七方面,在第七方面的某些实现方式中,所述第一指示信息用于指示所述终端设备在TA集合中的任一个TA内均允许发起对所述拒绝的切片中的任一个切片的连接请求,所述TA集合中的每一个TA均支持所述拒绝的切片中的至少一个切片,所述第二TA为所述TA集合中的任意一个。
结合第七方面,在第七方面的某些实现方式中,所述接收模块接收来自所述核心网设备的注册接受消息之前,所述发送模块,还用于向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
结合第七方面,在第七方面的某些实现方式中,所述第一能力指示信息携带于所述第一注册请求消息中。
第八方面,提供了一种终端设备,包括:
发送模块,用于当所述终端设备在第一跟踪区域TA内时,向核心网设备发送第一注册请求消息;
接收模块,用于接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系,所述第一切片属于所述拒绝的切片,所述第一RA包括第二TA;
所述接收模块还用于,通过所述第二TA的广播消息接收到所述第一NSASG的信息;
所述发送模块还用于,在所述终端设备根据所述第一指示信息驻留到所述第二TA时,向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
结合第八方面,在第八方面的某些实现方式中,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
结合第八方面,在第八方面的某些实现方式中,所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
结合第八方面,在第八方面的某些实现方式中,所述接收模块接收来自所述核心网设备的注册接受消息之前,所述发送模块,还用于向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
结合第八方面,在第八方面的某些实现方式中,所述第一能力指示信息携带于所述第一注册请求消息中。
第九方面,提供了一种核心网设备,包括:
接收模块,用于接收来自终端设备的第一注册请求消息;
发送模块,用于向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,
所述第一指示信息用于指示第二TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;或者,
所述第一指示信息用于指示所述终端设备在第二TA内允许发起对所述拒绝的切片中的任意一个切片的连接请求,所述第二TA属于所述第一RA并支持所述拒绝的切片中的至少一个切片,所述拒绝的切片包括第一切片;或者,
所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系,所述第一切片属于所述拒绝的切片,所述第一RA包括第二TA;
所述接收模块还用于,接收来自所述终端设备的第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
结合第九方面,在第九方面的某些实现方式中,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识;或者,所述第一指示信息包括所述第二TA的标识;或者,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
结合第九方面,在第九方面的某些实现方式中,所述第一指示信息包括多个TA对所述拒绝的切片的支持信息,所述多个TA中的每一个TA均属于所述第一RA并支持拒绝的切片中的至少一个切片,所述第二TA为所述多个TA中的任意一个;或者,
所述第一指示信息用于指示所述终端设备在TA集合中的任一个TA内均允许发起对所述拒绝的切片中的任一个切片的连接请求,所述TA集合中的每一个TA均支持所述拒绝的切片中的至少一个切片,所述第二TA为所述TA集合中的任意一个;或者,
所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
结合第九方面,在第九方面的某些实现方式中,所述接收模块还用于,接收来自所述终端设备的第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力;
所述发送模块具体用于,根据所述第一能力指示信息向所述终端设备发送所述注册接受消息。
结合第九方面,在第九方面的某些实现方式中,所述第一能力指示信息携带于所述第一注册请求消息中。
第十方面,提供了一种核心网设备,包括:
接收模块,用于接收来自终端设备的第一注册请求消息,所述第一注册请求消息包括第一能力指示信息,所述第一能力指示信息用于指示所述终端设备是否具备接收第一指示信息的能力;
发送模块,当所述第一能力指示信息指示终端设备具备接收所述第一指示信息的能力时,用于向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二跟踪区域TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;或者,
所述第一指示信息用于指示所述终端设备在第二TA内允许发起对所述拒绝的切片中的任意一个切片的连接请求,所述第二TA属于所述第一RA并支持所述拒绝的切片中的至少一个切片,所述拒绝的切片包括第一切片;或者,
所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系,所述第一切片属于所述拒绝的切片,所述第一RA包括第二TA;
当所述第一能力指示信息指示终端设备不具备接收所述第一指示信息的能力时,所述发送模块用于向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息以及第二RA的信息,所述第二RA中的任意一个TA均不支持所述拒绝的切片。
结合第十方面,在第十方面的某些实现方式中,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识;或者,所述第一指示信息包括所述第二TA的标识;或者,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
结合第十方面,在第十方面的某些实现方式中,所述第一指示信息包括多个TA对拒绝的切片的支持信息,所述多个TA中的每一个TA均属于所述第一RA并支持拒绝的切片中的至少一个切片,所述第二TA为所述多个TA中的任意一个;或者,
所述第一指示信息用于指示所述终端设备在TA集合中的任一个TA内均允许发起对所述拒绝的切片中的任一个切片的连接请求,所述TA集合中的每一个TA均支持所述拒绝的切片中的至少一个切片,所述第二TA为所述TA集合中的任意一个;或者,
所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
第十一方面,本申请实施例提供一种通信装置。该通信装置可以为终端设备,或者为设置在终端设备中的芯片。该通信装置包括:处理器、存储器和收发器;
收发器用于进行消息的接收和发送;
存储器用于存储指令;
处理器用于执行存储器存储的指令,当处理器执行存储器存储的指令时,使通信装置执行前述第一方面至第三方面中的任意一种实现方式所执行的方法。
第十二方面,本申请实施例提供一种通信装置。该通信装置可以为核心网设备,或者为设置在核心网设备中的芯片。该通信装置包括:处理器、存储器和收发器;
收发器用于进行消息的接收和发送;
存储器用于存储指令;
处理器用于执行存储器存储的指令,当处理器执行存储器存储的指令时,使通信装置执行前述第四方面至第五方面中的任意一种实现方式所执行的方法。
第十三方面,提供了一种终端设备,包括至少一个处理器,所述至少一个处理器用于与存储器耦合,读取并执行所述存储器中的指令,以实现前述第一方面至第三方面中的任意一种实现方式所执行的方法。
可选地,终端设备还包括该存储器。
第十四方面,提供了一种核心网设备,包括至少一个处理器,所述至少一个处理器用于与存储器耦合,读取并执行所述存储器中的指令,以实现第四方面至第五方面中的任意一种实现方式所执行的方法。
可选地,终端设备还包括该存储器。
第十五方面,提供了一种计算机程序产品,所述计算机程序产品包括:计算机程序代码,当所述计算机程序代码在计算机上运行时,使得计算机执行上述第一方面至第五方面中的任意一种实现方式所执行的方法。
需要说明的是,上述计算机程序代码可以全部或者部分存储在第一存储介质上,其中第一存储介质可以与处理器封装在一起的,也可以与处理器单独封装,本申请对此不作具体限定。
第十六方面,提供了一种计算机可读介质,所述计算机可读介质存储有程序代码,当所述计算机程序代码在计算机上运行时,使得计算机执行上述第一方面至第五方面中的任意一种实现方式所执行的方法。
第十七方面,提供了一种芯片系统,包括处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片系统的通信设备执行使得计算机执行上述第一方面至第五方面中的任意一种实现方式所执行的方法。
第十八方面,提供了一种通信系统,该通信系统包括上述第一方面至第三方面提供的终端设备、第五方面或第六方面提供的核心网设备中的至少一种。
图1是5G通信系统的网络架构示意图。
图2是网络切片的一例的示意图。
图3是终端设备在注册过程中切片的选择流程示意图。
图4是本申请的一种可能的应用场景的示意图。
图5是本申请实施例提供的通信方法的一例的示意性流程图。
图6是本申请实施例提供的通信方法的另一例的示意性流程图。
图7是本申请实施例提供的通信方法的再一例的示意性流程图。
图8是本申请实施例提供的通信方法的再一例的示意性流程图。
图9是本申请实施例提供的通信方法的再一例的示意性流程图。
图10是本申请实施例提供的终端设备的示意性框图。
图11是本申请实施例提供的终端设备的结构示意图。
图12是本申请实施例提供的核心网设备的示意性框图。
图13是本申请实施例提供的核心网设备的结构示意图。
为了使本申请实施例的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施例作进一步地详细描述。
本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通讯(global system for mobile communications,GSM)系统、码分多址(code division multiple access,CDMA)系统、宽带码分多址(wideband code division multiple access,WCDMA)系统、通用分组无线业务(general packet radio service,GPRS)、长期演进(long term evolution,LTE)系统、LTE频分双工(frequency division duplex,FDD)系统、LTE时分双工(time division duplex,TDD)、通用移动通信系统(universal mobile telecommunication system,UMTS)、全球互联微波接入(worldwide interoperability for microwave access,WiMAX)通信系统、第五代(5th generation,5G)通信系统、新无线接入技术(new radio access technology,NR),及未来的通信系统(如第六代(6th generation,6G)通信系统)等。
本申请以5G通信系统进行举例说明。图1是5G通信系统的网络架构示意图。图中示出了5G架构中的部分网元,该网络架构包括终端设备、接入网设备、接入管理网元、网络切片选择网元、数据管理网元以及网络存储网元,下面对各个设备或网元的功能进行简单介绍说明。
本申请中的终端设备是一种具有无线收发功能的设备,也可以称为用户设备(user equipment,UE)。终端设备可以部署在陆地上,包括室内或室外、手持或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtualreality,VR)终端、增强现实(augmented reality,AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportationsafety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
本申请中的接入网设备是一种为终端提供无线通信功能的设备,也可以称为无线接入网(radio access network,RAN)设备。接入网设备包括但不限于:5G中的下一代基站(gnodeB,gNB)、演进型节点B(evolved node B,eNB)、无线网络控制器(radio networkcontroller,RNC)、节点B(node B,NB)、基站控制器(base station
controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved nodeB,或homenode B,HNB)、基带单元(baseBand unit,BBU)、传输点(transmitting and receivingpoint,TRP)、发射点(transmitting point,TP)、移动交换中心等。
接入管理网元,是由运营商网络提供的控制面网元,负责终端设备接入运营商网络的接入控制和移动性管理,例如包括移动状态管理,分配用户临时身份标识,认证和用户等功能。在5G通信系统中,该接入管理网元可以是接入与移动性管理功能(access andmobility management function,AMF)网元。在未来通信系统如6G中,接入管理网元仍可以是AMF网元,或者,还可以有其它的名称,本申请不做限定。
网络切片选择网元,可用于为终端的业务选择合适的网络切片。在5G通信系统中,网络切片选择网元可以是网络切片选择功能(network slice selection function,NSSF)网元。在未来通信系统如6G中,网络开放功能网元仍可以是NSSF网元,或者,还可以有其它的名称,本申请不做限定。
数据管理网元,用于生成认证信任状,用户标识处理(如存储和管理用户永久身份等),接入控制和签约数据管理等。在5G通信系统中,该数据管理网元可以是统一数据管理(unified data management,UDM)网元。在未来通信系统如6G中,数据管理网元仍可以是UDM网元,或者,还可以有其它的名称,本申请不做限定。
网络存储网元,可用于提供网元发现功能,基于其他网元的请求,提供网元类型对应的网元信息。网络存储网元还可用于提供网元管理服务,如网元注册、更新、去注册以及网元状态订阅和推送等。在5G通信系统中,该网络存储网元可以是网络注册功能(network repositoryfunction,NRF)网元。在未来通信系统如6G中,网络存储网元仍可以是NRF网元,或者,还可以有其它的名称,本申请不做限定。
会话管理功能(session management function,SMF)网元主要用于会话管理、UE的网际协议(Internet Protocol,IP)地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中,可用于实现会话管理网元的功能。
本申请实施例所述的终端设备可以是图1中所述的UE,本申请实施例所述的接入网设备可以是图1中所述的RAN。本申请实施例所述接入管理网元可以是图1中所示的AMF网元,也可以是未来通信系统中的具有上述AMF网元的功能的网元。本申请实施例所述的网络切片选择网元可以是图1中所示的NSSF网元,也可以是未来通信系统中的具有上述NSSF网元的功能的网元。本申请实施例所述的数据管理网元可以是图1中所示的UDM网元,也可以是未来通信系统中的具有上述UDM网元的功能的网元。本申请实施例所述的网络存储网元可以是图1所示的NRF网元,也可以是未来通信系统中的具有上述NRF网元的功能的网元。本申请实施例所述的会话管理功能网元可以是图1所示的SMF网元,也可以是未来通信系统中的具有上述SMF网元的功能的网元。
为方便说明,本申请后续,以接入管理网元为AMF网元,网络切片选择网元为NSSF网元,数据管理网元为UDM网元,网络存储网元为NRF网元,会话管理功能网元为SMF为例进行说明。进一步地,将AMF网元简称为AMF,NSSF网元简称为
NSSF,UDM网元简称为UDM,NRF网元简称为NRF,SMF网元简称为SMF,终端设备简称为UE,接入网设备简称为RAN。即本申请后续所描述的AMF均可替换为接入管理网元,NSSF均可替换为网络切片选择网元,UDM均可替换为数据管理网元,NRF均可替换为网络存储网元,SMF均可替代为会话管理功能网元,RAN均可替换为接入网设备,UE均可替换为终端设备。
需要说明的是,本申请实施例中,“网络切片”和“切片”是同一概念,指的是同一内容,在不同的地方使用其中一种描述,二者可以互换。
本申请实施例可应用于各种支持网络切片的通信系统中,例如,5G通信系统。术语“系统”可以和“网络”相互替换。本申请实施例描述的系统架构是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
如上介绍了本申请实施例涉及的一些基本概念,以及5G网络架构等内容。接下来,对本申请实施例的相关内容继续进行介绍。
在5G时代,将有数以千亿计的物联网设备接入网络,不同类型的应用场景对网络的需求是差异化的,有的甚至是相互冲突的。通过单一网络同时为不同类型的应用场景提供服务,会导致网络架构异常复杂、网络管理效率和资源利用效率低下。为此提出了网络切片技术,5G网络切片技术通过在同一网络基础设施上虚拟独立逻辑网络的方式为不同的应用场景提供相互隔离的网络环境,使得不同应用场景可以按照各自的需求定制网络功能和特性,能够切实保障不同业务的服务质量(quality of Service,QoS)需求。5G网络切片要实现的目标是将终端设备、接入网资源、核心网资源以及网络运维和管理系统等进行有机组合,为不同商业场景或者业务类型提供能够独立运维的、相互隔离的完整网络。
图2为网络切片的一种示意图。作为一个具体示例,图2包括三个网络切片,分别为关键(critical)机器类通信(machine type ofcommunication,MTC)切片、海量(massive)MTC切片以及移动宽带(mobile broadband,MBB)切片。在图2中,critical MTC切片对应的终端设备可以包括车辆等;massive MTC切片对应的终端设备可以包括一些测量表等,例如电表或燃气表;MBB切片对应的终端设备可以包括手机或个人计算机(personal computer,PC)等。
多种多样的场景对第三代合作伙伴计划(3rd generation partnershipproject,3GPP)生态系统提出了不同的需要:计费、策略、安全、移动性等。3GPP强调了网络切片之间不相互影响,例如突发的大量的抄表业务不应该影响正常的移动宽带业务。为了满足多样性需求和切片间的隔离,需要业务间相对独立的管理和运维,并提供量身定做的业务功能和分析能力。不同类型业务的实例部署在不同的网络切片上,相同业务类型的不同实例也可部署在不同的网络切片上。
当核心网部署了网络切片,在终端设备初始附着到网络时,就会触发网络切片的选择过程。网络切片的选择过程取决于用户的签约数据、本地配置信息、漫游协议、或运营商的策略等参数中的一种或多种,在网络切片的选择过程中,需要综合考虑以上参数,才能为终端设备选择最佳的切片类型。
当终端需要接入到某个网络切片时,终端可以提供请求的(requested)网络切片给核心网,用于核心网为终端选择网络切片实例。其中,终端请求的网络切片,可以用请求的网络切片选择辅助信息(requestednetwork slice selection assistance information,requestedNSSAI)来表示。Requested NSSAI是由一个或多个单个网络切片选择辅助信息(singlenetwork slice selection assistance information,S-NSSAI)构成,即NSSAI是一组S-NSSAI的集合。每个S-NSSAI用于标识一个网络切片类型,也可以理解为,S-NSSAI用于标识网络切片,或者可以理解为S-NSSAI是网络切片的标识信息。在本申请的表述中,多个是指两个或者两个以上,例如可以是3个、4个或者5个。
一个网络切片是用S-NSSAI用来标识,S-NSSAI由切片类型/业务类型(slice/service type,SST)和切片差异化标识(slice differentiator,SD)组成。其中,SST用于描述切片在特性和业务方面的特征,表示期望网络可以提供的特征以及服务。SD可以作为选择网络切片实例(network slice instances,NSI)时对SST的补足信息。例如,当SST指向多个NSI的时候,SD可以进一步对这些NSI进行划分。即SD作为可选信息,用于区分具有相同SST特征的不同网络切片。
在5G网络中,当终端设备需要使用网络服务,需要首先向网络进行注册。图3是终端设备在注册过程中切片的选择流程示意图。如图3所示,终端设备在注册时就进行了切片请求,而核心网设备则向终端设备反馈其可使用的允许的切片(allowedNSSAI),后续终端设备进行业务时,只能从允许的切片中选取切片建立分组数据单元(packet data unit,PDU)会话。具体过程如下:
步骤1,UE向RAN发送注册请求(registration request)消息,RAN接收来自UE的注册请求消息。
该注册请求消息中携带有请求的切片(requestedNSSAI),该请求的切片为终端设备期望建立的PDU会话的网络切片。请求的切片用于指示在注册过程中终端设备提供给服务公共陆地移动网络的网络切片,例如,请求的切片是UE签约时确定的自身所支持的切片。该请求的切片包括一个或者多个切片(S-NSSAI),一个S-NSSAI可用于标识一个网络切片。
步骤2,RAN将该注册请求发送给初始(initial)AMF,初始AMF接收来自RAN的注册请求消息。
即RAN将注册请求消息转发给初始AMF。注册请求消息例如为N1消息(message)。在N1消息中,可以包括N1参数、注册消息、该终端设备的接入信息、PDU会话信息以及该UE的上下文请求等信息。
步骤3,初始AMF向UDM发起请求,获取UE的签约信息,该签约信息中包括UE的签约NSSAI等信息。
步骤4,初始AMF无法决定UE的允许的切片,则向NSSF请求切片选择,向NSSF发送UE请求的切片,UE签约的切片,UE的位置信息。
步骤5,NSSF确定UE允许的切片。此外,如果需要切换AMF则NSSF还需要确定目标(target)AMF。此时,NSSF将允许的切片、目标AMF的集合/列表,以及目标AMF对应的NRF的标识(identification,ID)等信息一并发送给初始AMF。
在这里,允许的切片用于指示UE在当前注册区域(registration area,RA)中所
有跟踪区域(tracking area,TA)都可使用的切片。其中,允许的切片包含请求的切片中所包含的至少一个切片。
相对地,核心网设备还可以维护拒绝UE接入的网络切片,该部分网络切片可以被称为拒绝的切片(rejectedNSSAI),其中可以包括一个或多个切片(S-NSSAI)。拒绝的切片中的切片可以是当前网络或当前TA不支持的网络切片。目前,拒绝的切片一般是基于UE注册请求中携带的请求的切片而确定的,当UE请求接入某一个网络切片时,若当前网络或当前TA不支持该网络切片,则将该网络切片添加到拒绝的切片列表中。
其中,TA是通信系统中位置管理的基本单位,由一个或多个小区组成。小区是一个无线接入网设备所覆盖的区域或者是无线接入网设备所覆盖的一部分区域,TA可以包含多个无线接入网设备包括的小区。当处于空闲态的终端设备需要被寻呼时,寻呼消息将以TA为单位进行寻呼,对一个终端设备的寻呼消息将在TA中的所有小区中发送。一个小区只能属于一个TA。
一个网络切片可以为一个或多个TA提供服务,一个TA可以支持一个或多个网络切片。TA可以利用跟踪区标识(tracking area identifier,TAI)或跟踪区编号(tracking area code,TAC)进行标识。其中TAI包括移动国家编号(mobile country code,MCC)、移动网络编号(mobile network code,MNC)和TAC。
RA由一个或多个TA组成。例如,终端设备在同一个RA中不同TA中移动时,不需要执行移动性注册更新。只有当终端设备移动至新的TA,且确定新的TA不属于RA时,才需要执行移动性注册更新。
步骤6,如果需要切换AMF,初始AMF根据NSSF发送的NRF标识向对应的NRF查询目标AMF的相关信息。
步骤7a,初始AMF向目标AMF发送AMF重置(relocation)请求消息,该重置请求消息用于请求为UE重置(更新)AMF。该AMF重置请求消息中携带有允许的切片的指示信息。
作为一个可选步骤,如图3所示,可以通过步骤7b替换步骤7a。在步骤7b中,初始AMF也可以通过RAN将AMF重置请求消息发送至目标AMF。该AMF重置请求消息中同样携带有允许的切片的指示信息。
步骤8,目标AMF向RAN发送注册接受(registration accept)消息,RAN接收来自于目标AMF的注册接受消息。注册接受消息用于通知UE的注册请求被接受。该注册接受消息中包括允许的切片、为UE分配的RA以及拒绝的切片等相关信息。例如,目标AMF通过N2消息向RAN发送该注册接受消息。
在完成AMF切换流程以后,目标AMF可以根据允许的切片来给UE分配(allocate)RA。AMF可以查询周围的多个TA中各个TA所支持的网络切片的情况,AMF将支持允许的切片的多个TA组成UE的RA。
以一个具体的示例来说明,表1示出了不同TA对网络切片的支持情况,NSSF确定允许的切片仅包括切片#1,此时,AMF可以查询周围多个TA中各个TA所支持的网络切片的情况,并将支持切片#1的3个TA(即TA#1、TA#2以及TA#3)组成RA#1,该RA#1即核心网为UE分配的注册区域。而TA#4由于不支持切片#1,因此无法被分
配至RA#1内。
表1:
步骤9,RAN将该注册接受消息发送至UE,UE接收来自于RAN的注册接受消息。即RAN将前述的注册接受消息转发至UE。
值得一提的是,通常情况下,UE可能并不需要切换AMF。此时,前述的步骤6、7(包括7a或者7b)可以省略。作为步骤8的替换步骤,可以由初始AMF将前述的注册接受消息发送给RAN,RAN将该注册接受消息转发至UE。
根据最新的协议进展,终端设备可能会在如下五种场景中向核心网发起注册流程:
(1)终端设备初次注册到5G网络;
(2)当终端设备移动到原来的注册区域(registration area,RA)以外的跟踪区域(tracking area,TA)中,引起的移动性注册更新;
(3)终端设备能力变化进行的更新;
(4)终端设备在非激活态的周期性注册更新;
(5)紧急注册。
根据前文的表述,UE在注册流程中才会进行网络切片选择,而UE触发注册流程的条件只有上述五种情况,所以UE可以进行allowed NSSAI切片选择的场景仅有上述几种场景。
图4是本申请的一种可能的应用场景的示意图。基于目前的协议,如图4所示,可能会存在如下场景:
TA#1支持切片#1,TA#2支持切片#1和切片#2。在这里,TA#1支持切片#1可以理解成切片#1在TA#1内可用,TA#2支持切片#1和切片#2可以理解成切片#1和切片#2在TA#2内可用。UE在TA#1内接入网络并进行注册流程,UE的请求的切片为切片#1和切片#2,但因为TA#1只支持切片#1,所以允许的切片为切片#1,拒绝的切片I为切片#2。核心网为UE分配RA时,因为TA#2也支持切片#1,所以将TA#1和TA#2都划分在RA#1中,RA#1即核心网为UE分配的注册区域,RA#1至少包括TA#1和TA#2在内的多个TA。
UE在RA#1内移动,当从TA#1移动到TA#2范围内,TA#2同时也支持切片#2,此时由于TA#2被划分在RA#1范围内,UE未出RA#1的范围内,不会重新发起注册流程,所以仍不会接入切片#2。而且因当前切片#2为拒绝的切片,UE也不会请求建立切片#2的会话。如果UE仍然想接入切片#2,UE需要移动至位于RA#1范围外并支持切片#2的TA#3范围内,此时UE才可以重新发起注册流程,尝试接入切片#2。
综上所述,在请求的切片包含多个切片,且核心网设备发送的允许的切片包含请求的切片中的部分切片的情况下,则终端设备请求的切片包含的另一部分切片不在允许的切片中,这样即使终端设备处在支持使用另一部分的切片(即拒绝的切片)的TA
内时,该终端设备也不被允许使用该另一部分切片。这一方式限定了终端设备在当前的网络覆盖范围内可以使用的网络切片的数量或类型,也限定了终端设备所能建立的PDU会话的类型,无法满足终端设备通过使用网络切片进行通信的需求。
在这种情形下,如何更好地满足终端设备通过使用网络切片进行通信的需求成为有待解决的技术问题。
基于上述问题,本申请实施例提供一种通信方法以及终端设备、核心网设备,能够扩大终端设备在当前的网络覆盖范围内可以使用的网络切片的数量或类型,也增加了终端设备所能建立的PDU会话的类型,能够更大程度的满足终端设备通过使用网络切片进行通信的需求,从而提高了用户体验。
可以理解的,本申请实施例中,终端设备和/或核心网设备(例如,AMF)可以执行本申请实施例中的部分或全部步骤,这些步骤或操作仅是示例,本申请实施例还可以执行其它操作或者各种操作的变形。此外,各个步骤可以按照本申请实施例呈现的不同的顺序来执行,并且有可能并非要执行本申请实施例中的全部操作。核心网设备可以仅包括一个核心网网元(例如AMF),例如也可以由多个核心网网元(例如前述的初始AMF、目标AMF以及NSSF中的至少两个)共同构成,本申请对此不做特殊限定。
下面结合附图介绍本申请实施例提供的通信方法,实施例中的核心网设备以AMF为例进行说明。图5是本申请提供的通信方法500的示意性流程图。以下,结合图5阐述本申请实施例提供的通信方法500,该方法500包括:
步骤501,终端设备在第一跟踪区域TA内向AMF发送第一注册请求消息,AMF接收来自终端设备的第一注册请求消息。
本申请实施例提供的方法500可以应用于终端设备向核心网发起注册流程的场景。终端设备触发该注册流程的条件可以是前述五个条件中的任意一个,例如,终端设备移动到原来的注册区域RA以外的TA(即第一TA)中,引起了移动性注册更新,因此需要向核心网发起新的注册流程。在本申请实施例中,终端设备触发注册流程的条件不限于上述五个,随着3GPP标准的不断演进,还可以是未来其他任意条件触发的注册流程。
终端设备通过第一TA内的小区接入网络并进行注册流程,终端设备可以经由无线接入网设备(RAN)向AMF发送第一注册请求消息。相应地,AMF经由无线接入网设备接收该注册请求消息。这里的注册请求消息未来还可以以其他名称命名,本申请实施例对此不做限定。
其中,第一注册请求消息包括请求的切片(requested NSSAI)的信息,请求的切片可以包括多个切片,此时第一注册请求消息可以包括多个切片对应的标识(例如SST和SD)。第一注册请求消息例如为N1消息,即终端设备可以通过N1接口将第一注册请求消息发送给AMF。
步骤502,AMF确定允许的切片(allowedNSSAI)和拒绝的切片(rejectedNSSAI)。
AMF接收到第一注册请求消息后,为终端设备进行切片选择(sliceselection)。AMF根据终端设备的签约数据、请求的切片、漫游协议以及本地配置等信息综合判断,为终端设备选择允许的切片和拒绝的切片。
AMF可以将请求的切片中的一个或者多个切片所组成的集合确定为允许的切片,即允许的切片可以为请求的切片中所包含的切片的子集或全集。在此基础之上,AMF可以将请求的切片中剩余的切片所组成的集合确定为拒绝的切片。例如,可以将请求的切片中当前TA(即第一TA)所不支持的切片确定为拒绝的切片。
为了更加方便高效的阐述本申请技术方案,作为一个具体的示例,表2为不同类型切片与具体切片的对应关系表。如表2所示,位于TA#1(即第一TA)内的终端设备向AMF发送第一注册请求消息,第一注册请求消息包括请求的切片,请求的切片包括切片#1、切片#2和切片#3共三个切片,AMF确定终端当前所处的TA#1仅支持切片#3,而不支持另外两个,因此确定切片#3为允许的切片,而切片#1、切片#2这两个切片共同构成了拒绝的切片。即切片#1和切片#2均为被拒绝的切片。
表2:
步骤503,AMF根据允许的切片分配第一注册区域RA作为终端设备当前的RA。
具体地,AMF可以根据允许的切片来给终端设备分配(allocate)RA。AMF可以查询第一TA周围的多个TA中各个TA所支持的切片的情况,AMF将支持允许的切片中的至少一个切片的多个TA组成第一RA,并且分配给终端设备。也就是说,对于第一RA中的每一个TA,均应当支持允许切片中的至少一个切片。在这里,某个TA支持某一个切片,也可以理解成该切片在该TA内可用。TA不支持某一个切片,也可以理解成该切片在该TA内不可用。
以一个具体的示例来说明,表2同时示出了AMF查询到的不同TA对切片的支持情况。AMF共查询到包括TA#1~TA#7在内的7个TA。其中,TA#1即终端发起注册请求的TA,即TA#1即第一TA。AMF确定允许的切片仅包括切片#3这一个,对于AMF查询到的TA#1周围的TA#2~TA#7,其中支持切片#3的TA为TA#2~TA#5,因此AMF将TA#1~TA#5共五个TA组成第一RA。而TA#6、TA#7由于不支持切片#3,因此无法被分配至第一RA内。
以上示例中多个TA的数量仅为举例说明,本申请不限定AMF所查询的TA的数量,也不限定RA内所包含的TA的数量。可选地,AMF可以向NSSF或者其他核心网网元查询TA以及在该TA终可以使用的网络切片的相关信息。
可选地,在其他实现方式中,AMF可能无法独立完成上述步骤502和步骤503,此时可以借助NSSF、UDM等网元一起来完成。例如,上述步骤中的至少一个可以完
全由NSSF来完成,NSSF可以将相应的结果告知AMF。具体可以参考前述对步骤4和步骤5的描述。由AMF和NSSF、UDM共同完成切片选择以及为终端设备分配RA属于现有技术,在此不再赘述。
例如,AMF还可以与NSSF进行信息交互,从NSSF获取允许的切片和拒绝的切片的信息。此时决策网元为NSSF,AMF可以接收并且转发该消息。
步骤504,AMF向终端设备发送注册接受消息,终端设备接收来自AMF的注册接受消息,该注册接受消息可以包括允许的切片的信息、拒绝的切片的信息以及第一RA的信息。
该注册请求消息用于应答第一注册请求消息。AMF在确定好允许的切片、拒绝的切片以及第一RA以后,可以将上述信息携带于注册接受消息中,通过注册接受消息发送至终端设备。AMF可以经由无线接入网设备(RAN)向终端设备发送注册接受消息。相应地,终端设备经由无线接入网设备接收该注册接受消息。这里的注册接受消息未来还可以以其他名称命名,本申请实施例对此不做限定。注册接受消息例如可以为N2消息,即AMF可以通过N2接口将注册接受消息发送给终端设备。
可选地,允许的切片可以包括一个或者多个切片,注册接受消息可以包括上述一个或者多个切片的标识信息。根据前述示例,允许的切片包括切片#3,则注册接受消息的相应的信元(或比特位)上可以携带切片#3的标识,例如,该标识可以是S-NSSAI。
可选地,拒绝的切片可以包括一个或者多个切片,注册接受消息可以包括上述一个或者多个切片的标识信息。根据前述示例,拒绝的切片包括切片#1和切片#2,则注册接受消息的相应的信元(或比特位)上可以携带切片#1和切片#2的标识,例如该标识可以是S-S-NSSAI。
可选地,第一RA包括第一TA在内的多个TA,第一RA的信息可以包括该第一RA中包含的多个TA中各个TA的标识信息。TA的标识例如可以是TAI或者TAC。根据前述示例,第一RA的信息可以包括TA#1~TA#5的标识,即注册接受消息的相应的信元(或比特位)上可以携带TA#1~TA#5的标识。
进一步地,如图5所示,区别于现有技术,本申请实施例中的注册接受消息还携带有第一指示信息,第一指示信息用于指示第二TA支持第一切片,第二TA属于第一RA中的一个,第一切片属于拒绝的切片中的一个。
可选地,该第一指示信息可以由AMF自行判断并生成,也可以由NSSF判断并生成,本申请对此不做特殊限定。
例如,可以由NSSF来判断并生成允许的切片、拒绝的切片以及第一RA等相关信息,而第一指示信息由AMF生成并且添加到注册接受消息中。
步骤505,终端设备继续进行其他注册流程,以完成注册。此时,终端设备可以使用允许的切片中的一个或者多个切片建立PDU会话(PDU session)。当然,如果终端设备当前没有业务需求,也可以不使用允许的切片中的切片。
步骤506,当终端设备从第一TA移动至第二TA时,终端设备可以根据第一指示信息向AMF发送第二注册请求消息,第二注册请求消息包括第一切片的信息。
具体地,当终端设备从第一TA移动至第二TA内时,并且终端设备根据当前业务需求(例如某个应用程序(application,APP)的使用需求)确定需要接入第一切片
以建立PDU会话,而根据第一指示信息的指示,终端设备能够获知当前所处的第二TA支持第一切片,由于第一切片在当前的RA(第一RA)内为拒绝使用的切片,因此终端设备自行触发注册流程,再次向AMF发送注册请求消息(即第二注册请求消息),第二注册请求消息中携带的请求的切片包括第一切片,待获得AMF的批准后,终端设备则可以接入该第一切片以进行通信。例如第二注册请求消息包括第一切片的标识,例如该标识可以是第一切片的S-NSSAI。
根据本申请实施例提供的通信方法500,注册接受消息中还携带有第一指示消息,根据该第一指示消息终端设备能够知道某个具体的被拒绝的切片在哪个TA中可用,例如根据该第一指示信息终端能够知道被拒绝的第一切片其实在第二TA中是可用的,这样当终端设备移动至第二TA内以后,如果仍然想使用第一切片进行网络通信(例如建立PDU会话),则可以再次发起注册请求,请求能够接入第一切片。通过以上设置能够扩大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,也增加了终端设备所能建立的PDU会话的类型,从更大程度上满足了终端设备通过使用网络切片进行通信的需求,从而提高了用户体验。
作为一个具体的示例,如表2所示,第一切片为表2中的切片#1,第二TA为表2中的TA#2,则第一指示信息指示给终端设备TA#2是支持切片#1的,即切片#1在TA#2内是可用的。当终端设备从发第一起注册请求消息的TA#1内移动至TA#2(期间可以驻留或者经过其他TA)以后,终端设备如果因为业务需求仍然想接入到切片#1内,则可以再次发起注册请求,以请求能够接入到切片#1。
可选地,当终端设备从第一TA移动至第二TA内,如果终端设备判定除了第一切片以外还想接入其他的切片,则此时第二注册请求消息中的请求的切片除了包括第一切片以外,还可以包括其他的切片,本申请对此不作特殊限定。
可选地,当终端设备从第一TA移动至第二TA内,如果终端设备判定当前没有接入到第一切片的需求(不想使用第一切片),则可以不向AMF发送第二注册请求消息,即此时终端设备可以不作任何动作,步骤506可以省略。
值得一提的是,本申请实施例中的通信方法500实际上提供了另一个能够触发终端设备向核心网发起注册流程的条件。即除了前述的五个条件以外,本申请实施例提供的通信方法500可以作为终端设备触发注册流程的第六个条件。在此基础之上,对于方法500中的步骤501,即终端设备向AMF发送第一注册请求消息,也可以是终端设备根据第一指示消息而自动触发的注册流程。即在步骤501中,如果终端设备想使用某个之前RA内被拒绝的切片,而终端又知道当前所处的第一TA支持该被拒绝的切片,因此发送第一注册请求消息,请求接入该被拒绝的切片。
可选地,第一指示信息可以作为一个独立的信元携带于注册接受消息中,第一指示信息可以包括第二TA的标识和第一切片的标识。
例如,第二TA的标识可以是第二TA的TAI或者TAC,而第一切片的标识可以是第一切片的S-NSSAI。
可选地,拒绝的切片的信息、第一RA的信息以及第一指示信息这三个信息可以作为三个独立的信元携带于注册接受消息中,或者其中的两个或者三个信息也可以被携带于同一个信元内(好处是有利于减小整个注册接受消息的体积)。也就是说,其
中的两个或者三个信息可以共用一个信元,本申请对注册接受消息的具体实现方式不作特殊限定。
可选地,第二TA可以是第一RA内支持拒绝的切片中至少一个切片的多个TA中的任意一个。例如,如表2所示,第二TA可以是TA#2、TA#3以及TA#5中的任意一个。
可选地,第二TA可以仅支持拒绝的切片中的一个切片,则此时第一切片为第二TA所支持的唯一的一个切片。
例如,如表2所示,第二TA可以是TA#2,TA#2仅支持拒绝的切片中的切片#1,则此时第一切片为切片#1。
再例如,如表2所示,第二TA可以是TA#3,TA#3仅支持拒绝的切片中的切片#2,则此时第一切片为切片#2。
可选地,第二TA可以支持拒绝的切片中的多个切片,则此时第一切片可以为第二TA所支持的多个切片中的任意一个。
例如,如表2所示,第二TA可以是TA#5,TA#5支持拒绝的切片中的切片#1和切片#2,则此时第一切片可以为切片#1或者切片#2。
可选地,当第二TA支持拒绝的切片中的多个切片时,第一指示信息可以指示第二TA所支持的该多个切片种的多个或者全部(第一切片为其中的一个)。
例如,第二TA可以是TA#5,TA#5支持拒绝的切片中的切片#1和切片#2,此时第一指示信息可以指示TA#5支持切片#1和切片#2。
以上设置的好处是,由于第一指示信息的信息量变大,终端设备能够根据第一指示信息获知多个被拒绝的切片能够在第二TA中可用,如此在移动到第二TA内以后,终端设备如果想使用该多个被拒绝的切片中的至少一个切片进行通信的情况下,即可以再次发起注册请求,请求能够接入相应的切片。由此能够更大程度的增大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,更大程度的满足终端设备通过使用网络切片进行通信的需求,进一步提高用户体验。
可选地,第一指示信息包括多个TA对拒绝的切片的支持信息,该多个TA中的每一个TA均属于第一RA并支持拒绝的切片中的至少一个切片,第二TA为多个TA中的任意一个。
也就是说,第一指示信息具有更大的信息量,能够同时指示多个TA对拒绝的切片的支持情况,例如其中一个TA支持具体的哪个或者哪些切片,另一个TA支持具体的哪个或者哪些切片。当终端设备移动至其中的一个TA内以后,终端设备根据实际需求确定需要接入该TA所支持的一个或者多个拒绝的切片,则可以发起第二注册请求消息,请求接入相应的切片。以上设置使得第二注册请求消息的发送概率和频次大大增加,即发送对拒绝的切片的接入请求的概率和频次也大大增加,由此能够更大程度的增大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,更大程度的满足终端设备通过使用网络切片进行通信的需求,进一步提高用户体验。
可选地,第一指示信息还用于指示第三TA支持第二切片,第三TA属于第一RA,第二切片为拒绝的切片中的一个,第二切片与第一切片可以相同也可以不同。
例如,如表2所示,第二TA可以是TA#2,TA#2仅支持拒绝的切片中的切片#1,
则此时第一切片为切片#1。第三TA可以是TA#5,TA#5支持拒绝的切片中的切片#1和切片#2,则此时第二切片可以为切片#1或者切片#2。
类似地,当第三TA支持拒绝的切片中的多个切片时,第一指示信息可以指示第三TA所支持的该多个切片中的多个或者全部(第二切片为其中的一个)。
可选地,第一指示信息包括多个TA对拒绝的切片的支持信息,该多个TA为第一RA内支持拒绝的切片中至少一个切片的所有TA。
例如,如表2所示,在第一RA内,TA#2、TA#3以及TA#5支持至少一个拒绝的切片,则第一指示信息包括这三个TA对对拒绝的切片的支持信息。即第一指示信息可以同时指示这三个TA支持哪一个或者哪些切片。
可选地,第一指示信息包括多个TA对拒绝的切片的支持信息,所示支持信息用于指示多个TA中的每一个TA支持所述拒绝的切片中的至少一个切片,或者用于指示多个TA中的每一个TA所支持的所述拒绝的切片中的切片,该多个TA中的每一个TA均属于第一RA,该多个TA包括第二TA。
可选地,该支持信息可以包括多个TA的标识,以及多个被拒绝的切片的标识,多个TA标识与多个切片的标识具有映射(对应)关系,根据该支持信息,能够或者其中每个TA支持哪些被拒绝的切片,以及其中每个切片被哪些TA所支持。
作为一种可能的具体实现方式,第一指示信息可以以映射表的形式存在,该映射表中包括多个具体的TA与拒绝的切片的一一对应关系,并且按照一定的时序发送该映射表,例如:
TA#2:切片#1;TA#3:切片#2;TA#5:切片#1、切片#2;此时TA作为索引。或者:
切片#1:TA#2、TA#5;切片#2:TA#3、TA#5;此时切片作为索引。
进一步地,在步骤504,终端设备接收来自AMF的注册接受消息之前,也即AMF向终端设备发送注册接受消息之前,方法500还包括:
终端设备向核心网设备发送第一能力指示信息,第一能力指示信息用于指示终端设备具备接收第一指示信息的能力。AMF根据第一能力指示信息向终端设备发送该注册接受消息。
具体地,考虑到终端设备执行(支持)的协议版本可能不一致,例如有的终端执行较高版本的协议,而有的终端执行较低版本的协议,有些版本的协议可能并不支持终端接收该第一指示信息。因此,为了避免出现接收错误、接收无法识别等问题,本申请实施例提供的方法500还规定终端设备提前向AMF发送第一能力指示信息,以指示自身是否具备接收第一指示信息的能力。当确定终端设备具备接收第一指示信息的能力时,AMF向终端设备发送的注册接受消息中携带该第一指示信息。
可选地,该第一能力指示信息可以显性(直接)指示,例如按照协议或者系统的规定,为一串特定的代码,或者一比特的0或1,或者用NULL和非NULL区分。或者,该第一能力指示信息也可以隐含(间接)指示,本申请对此不作限定。
例如,第一能力指示信息可以包括一比特的1来指示终端设备具备接收第一指示信息的能力,用一比特的0来指示终端设备不具备接收第一指示信息的能力。
进一步地,第一能力指示信息可以携带于第一注册请求消息中。
可选地,第一能力指示信息也可以通过现有技术中的其他消息进行携带,或者终端设备可以单独向AMF发送该第一能力指示信息,本申请对此并不限定。
可选地,作为一种可能的替换方式,AMF也可以从其他核心网网元(例如NSSF)查询到终端设备的能力信息,根据该能力信息来确定终端设备是否具备接收第一指示信息的能力。此时终端设备向AMF发送第一能力指示信息的动作可以省略。
图6是本申请实施例提供的通信方法600的示意性流程图,图6所示实施例可以看作是图5所示实施例的一种变形方式。以下,结合图6说明本申请实施例提供的通信方法600,方法600包括:
步骤601,终端设备在第一跟踪区域TA内向AMF发送第一注册请求消息,第一注册请求消息中携带请求的切片。
相应地,在步骤601中,AMF接收来自于终端设备的第一注册请求消息。
可选地,第一注册请求消息中还可以携带第一能力指示信息,第一能力指示信息用于指示终端设备具备接收第一指示信息的能力。后续步骤中AMF可以根据第一能力指示信息向终端设备发送注册接受消息。
步骤602,AMF确定允许切片和拒绝的切片。
步骤603,AMF根据允许的切片分配第一注册区域RA作为终端设备的当前RA。
步骤604,AMF向终端设备发送注册接受消息,该注册接受消息包括允许的切片的信息、拒绝的切片的信息、第一RA的信息以及第一指示信息。
相应地,终端设备接收来自AMF的注册接受消息。
步骤605,终端设备继续进行其他注册流程,以完成注册。
步骤606,当终端设备从第一TA移动至第二TA时,终端设备根据第一指示信息向AMF发送第二注册请求消息,第二注册请求消息包括第一切片的信息(例如标识)。
相应地,AMF接收来自于终端设备的第二注册请求消息。
上述步骤601-606可以参照方法500中的步骤501-506进行理解,在此仅阐述不同之处。在本申请实施例中,和前述图5所示实施例不同的地方主要在于,方法600和方法500中的第一指示信息指示的内容有所不同,导致终端设备通过第二注册请求消息向AMF请求接入第一切片的成功率也有所不同。
具体地,在本实施例中,第一指示信息用于指示允许终端设备在第二TA内发起对拒绝的切片中的任意一个切片的连接请求,第二TA属于第一RA并支持拒绝的切片中的至少一个切片,拒绝的切片包括第一切片。
根据本申请实施例提供的方法600,注册接受消息中还携带有第一指示消息,第一指示信息仅向终端设备指示第二TA可能支持拒绝的切片中的某一个或者多个切片,而没有明确指示其支持的是具体的哪一个或者哪些。当终端设备移动至第二TA后,如果仍然想使用第一切片进行网络通信(例如建立PDU会话),终端设备自行触发注册流程,再次向AMF发送注册请求消息(即第二注册请求消息),第二注册请求消息中携带的请求的切片包括第一切片,待获得AMF的批准后,终端设备则可以接入该第一切片以进行通信。通过以上设置能够扩大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,也增加了终端设备所能建立的PDU会话的类型,从更大程度上满足了终端设备通过使用网络切片进行通信的需求,从而提高了用户体
验。
此外,相对于前述实施例,本实施例提供的方法600并不会开放第二TA对拒绝的切片的支持信息,可以保证不会开放运营商的切片部署信息给终端设备,具有更高的安全性能。当然,终端设备在第二TA内通过第二注册请求消息发起对第一切片的连接请求,可能会因为第二TA不支持第一切片而被拒绝。
例如,第一TA为表2中的TA#1,第二TA为TA#2,TA#2支持拒绝的切片中的切片#1。当终端设备由TA#1移动至TA#2内以后,确定自身需要接入切片#1(即第一切片为切片#1),则此时可以再次发起注册请求,请求能够接入切片#1。由于终端设备请求的第一切片(切片#1)为第二TA所支持的切片,因此AMF可以允许终端设备接入第一切片。
再例如,第一TA为表2中的TA#1,第二TA为TA#2,TA#2支持拒绝的切片中的切片#1。当终端设备由TA#1移动至TA#2内以后,确定自身需要接入切片#2(即第一切片为切片#2),则此时可以再次发起注册请求,请求能够接入切片#2。由于终端设备请求的第一切片(切片#2)不被第二TA所支持,因此AMF可能会拒绝终端设备接入第一切片。
可选地,第一指示信息可以作为一个独立的信元携带于注册接受消息中,此时第一指示信息可以包括第二TA的标识,例如TAI或者TAC。
可选地,第二TA可以是第一RA内支持拒绝的切片中至少一个切片的多个TA中的任意一个。例如,如表2所示,第二TA可以是TA#2、TA#3以及TA#5中的任意一个。
可选地,第一指示信息用于指示终端设备在TA集合或者列表(list)中的任一个TA内均允许发起对拒绝的切片中的任一个切片的连接请求,该TA集合或者列表中的每一个TA均支持拒绝的切片中的至少一个切片,第二TA为TA集合中的任意一个。
换句话说,第一指示信息可以指示多个TA中的每个TA内均允许终端设备发起对拒绝的切片中的任一个切片的连接请求。该多个TA中的每一个TA均支持拒绝的切片中的至少一个切片。此时,第一指示信息可以包括该多个TA的标识。
例如,如表2所示,TA#2、TA#3以及TA#5中的任意一个均支持拒绝的切片中至少一个,则该TA集合可以包括TA#2、TA#3以及TA#5中的多个或者全部。第一指示信息可以指示终端设备能够在TA#2、TA#3(此时TA集合包括TA#2和TA#3)中发起对拒绝的切片中的任一个切片的连接请求。第一指示信息可以包括TA#2和TA#3的标识信息。
通过以上设置,终端设备在移动到其中的任意一个TA内均可以发起对拒绝的切片中的任一个切片的连接请求,由此能够提高第二注册消息的发送频次,能够更大程度的增大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,更大程度的满足终端设备通过使用网络切片进行通信的需求,进一步提高用户体验。
可选地,第一指示信息包括TA集合,该TA集合包括允许终端设备发起对所述拒绝的切片中的任意一个切片的连接请求的TA的标识,该TA集合包括所述第二TA标识。
可选地,该TA集合可以是第一RA内支持拒绝的切片中至少一个切片的所有TA
的集合,例如,该TA集合可以包括表2中的TA#2、TA#3以及TA#5。
此时,AMF在向终端设备发送注册接受消息之前,可以首先确定该TA集合,例如将第一RA内支持拒绝的切片中至少一个切片的TA放入该集合中。例如确定第二TA属于第一RA并且支持拒绝的切片中的至少一个切片,因此可以将第二TA放置于该集合内。
图7是本申请实施例提供的通信方法700的示意性流程图,图7所示实施例可以看作是图5所示实施例的一种变形方式。以下,结合图7说明本申请实施例提供的通信方法700,方法700包括:
步骤701,终端设备在第一跟踪区域TA内向AMF发送第一注册请求消息,第一注册请求消息中携带请求的切片。
相应地,在步骤701中,AMF接收来自于终端设备的第一注册请求消息。
可选地,第一注册请求消息中还可以携带第一能力指示信息,第一能力指示信息用于指示终端设备具备接收第一指示信息的能力。后续步骤中AMF可以根据第一能力指示信息向终端设备发送注册接受消息。
步骤702,AMF确定允许切片和拒绝的切片。
步骤703,AMF根据允许的切片分配第一注册区域RA作为终端设备的当前RA。
步骤704,AMF向终端设备发送注册接受消息,该注册接受消息包括允许的切片的信息、拒绝的切片信息、第一RA的信息以及第一指示信息。其中,第一指示信息用于指示第一切片与第一网络切片接入层群组(network slice access stratum group,NSASG)之间具有映射关系,第一切片属于拒绝的切片,第一RA包括第二TA。
相应地,终端设备接收来自AMF的注册接受消息。
步骤705,终端设备继续进行其他注册流程,以完成注册。
步骤707,终端设备通过第二TA的广播消息接收到第一NSASG的信息。
步骤706,终端设备驻留到第二TA,并且根据第一指示信息向AMF发送第二注册请求消息,第二注册请求消息包括第一切片。
相应地,AMF接收来自于终端设备的第二注册请求消息。
上述步骤701-706可以参照方法500中的步骤501-506进行理解,在此仅阐述不同之处。在本申请实施例中,和前述图5所示实施例不同的地方主要在于,方法700和方法500中的第一指示信息指示的内容或形式有所不同。在本实施例中,第一指示信息用于指示第一切片与第一NSASG之间具有映射关系。
具体地,多个切片可以被映射为一个NSASG,然后该NSASG的信息会在RAN空口广播的消息中携带。终端设备可以通过空口监听到当前小区(cell)或TA对应的NSASG。也就是说,NSASG是以小区或者TA为粒度的,由于每个小区只能属于一个TA,因此NSASG与TA的关系可以是多对1或者1对1。
终端设备可以向核心网查询,或由核心网配置NSASG与切片的对应关系。例如,NSASG#1对应切片#1,切片#2,则广播NSASG1的小区或TA应支持切片#1和切片#2。但该对应关系需要由核心网进行配置和更新,并且终端设备无法从广播信息中获知该对应关系。
在步骤704中,AMF向终端设备发送第一指示信息,该第一指示信息用于指示第
一切片与第一NSASG之间具有映射关系,即指示第一NSASG对应的TA支持第一切片。并且第一切片属于拒绝的切片,第一RA包括第二TA。
可选地,在其他实现可能的方式中,第一切片也可以不属于拒绝的切片。
可选地,在其他可能的实现方式中,第二TA也可以不属于第一RA。
在步骤707中,终端设备通过第一RA的第二TA的广播消息接收到第一NSASG的信息,例如该第一NSASG的信息可以携带于广播消息中的系统消息块(例如系统信息块1(system information block 1,SIB1))中。
在步骤706中,终端设备接收到该第一NSASG的信息,并且根据第一指示信息能够确定第一NSASG的信息所对应的第二TA(即发送第一NSASG的信息的TA)能够支持第一切片。因此可以将终端设备驻留到第二TA(例如第二TA内的某个小区内),并且向AMF发送第二注册请求消息,第二注册请求消息包括第一切片的信息。待获得AMF的批准后,终端设备则可以接入该第一切片以进行通信。
根据本申请实施例提供的方法700,注册接受消息中还携带有第一指示消息,根据该第一指示消息终端设备能够知道某个具体的被拒绝的切片在哪个NSASG对应的TA内是可用的,例如根据该第一指示信息终端能够知道被拒绝的第一切片其实在第一NSASG对应的第二TA中是可用的,当终端设备通过第二TA的广播消息接收到第一NSASG的信息时,终端能够获知第二TA能够支持第一切片,这时如果确定自身仍然想使用第一切片进行网络通信(例如建立PDU会话),可以将终端设备驻留于第二TA内,并且再次发起注册请求,请求能够接入第一切片。通过以上设置能够扩大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,也增加了终端设备所能建立的PDU会话的类型,从更大程度上满足了终端设备通过使用网络切片进行通信的需求,从而提高了用户体验。
此外,方法700并没有开放具体的TA的切片部署情况给终端设备,仅提供了NSASG与拒绝的切片的映射关系,检测到NSASG广播信息时就可以触发对拒绝的切片的请求,而不用切换到对应的TA再触发,例如此时可以仅位于TA的边缘,更加灵活,适用更多的场景。
可选地,第一指示信息包括第一切片的标识和第一NSASG的标识。
可选地,第一指示信息可以用于指示第一切片与包括第一NSASG在内的多个NSASG之间均具有映射关系,即指示第一切片对应多个NSASG,第一NSASG可以是该多个NSASG种的任意一个。当终端设备接收到任一个NSASG的消息后,可以驻留到对应的TA中,并再次发起注册请求,请求能够接入第一切片。
可选地,第一指示信息可以用于指示包括第一切片在内的多个切片与第一NSASG之间具有映射关系,即指示多个切片对应第一NSASG,表明第一NSASG对应的TA可以支持多个切片。第一切片可以是该多个切片种的任意一个。
可选地,第一指示信息用于指示拒绝的切片中的多个切片(例如,全部)与NSASG的映射关系,第一切片为多个切片中的任一个。
通过以上设置使得第二注册请求消息的发送概率和频次大大增加,即发送对拒绝的切片的接入请求的概率和频次也大大增加,由此能够更大程度的增大终端设备在当前的无线网络覆盖范围内可以使用的网络切片的数量或类型,更大程度的满足终端设
备通过使用网络切片进行通信的需求,进一步提高用户体验。
作为一种可能的具体实现方式,第一指示信息可以以映射表的形式存在,该映射表中包括多个具体的切片与多个NSASG的对应关系,并且按照一定的时序发送该映射表,例如:NSASG#1:切片#1、切片#2或者切片#1:NSASG#1、NSASG#2等。
进一步地,在步骤704,终端设备接收来自AMF的注册接受消息之前,也即AMF向终端设备发送注册接受消息之前,方法700还包括:
终端设备向核心网设备发送第二能力指示信息,第二能力指示信息用于指示终端设备具备接收NSASG的信息的能力。AMF根据第二能力指示信息向终端设备发送该注册接受消息。
本申请实施例提供的方法700还规定终端设备提前向AMF发送第二能力指示信息,以指示自身是否具备接收NSASG的信息的能力。当确定终端设备具备接收NSASG的信息的能力时,AMF向终端设备发送的注册接受消息中携带该第一指示信息。
类似地,该第一能力指示信息可以显性(直接)指示,例如按照协议或者系统的规定,为一串特定的代码,或者一比特的0或1,或者用NULL和非NULL区分。或者,该第二能力指示信息也可以隐含(间接)指示,本申请对此不作限定。
例如,第二能力指示信息可以包括一比特的1来指示终端设备具备接收NSASG的信息的能力,用一比特的0来指示终端设备不具备接收NSASG的信息的能力。
进一步地,第二能力指示信息可以携带于第一注册请求消息中。
可选地,第二能力指示信息也可以通过现有技术中的其他消息进行携带,或者终端设备可以单独向AMF发送该第二能力指示信息,或者将第一能力指示信息和第二能力指示信息一起整合打包后发送给AMF,本申请对此并不限定。
可选地,作为一种可能的替换方式,AMF也可以从其他核心网网元(例如NSSF)查询到终端设备的能力信息,根据该能力信息来确定终端设备是否具备接收第二指示信息的能力。此时终端设备向AMF发送第二能力指示信息的动作可以省略。
图8是本申请实施例提供的通信方法800的示意性流程图,图8所示实施例可以看作是图5所示实施例的一种变形方式。以下,结合图8说明本申请实施例提供的通信方法800,方法800包括:
步骤801,终端设备在第一跟踪区域TA内向AMF发送第一注册请求消息,第一注册请求消息中携带请求的切片。
相应地,在步骤801中,AMF接收来自于终端设备的第一注册请求消息。
可选地,第一注册请求消息中还可以携带第一能力指示信息,第一能力指示信息用于指示终端设备具备接收第一指示信息的能力。后续步骤中AMF可以根据第一能力指示信息向终端设备发送注册接受消息。
步骤802,AMF确定允许切片和拒绝的切片。
步骤803,AMF根据允许的切片分配第一注册区域RA作为终端设备的当前RA。
步骤804,AMF向终端设备发送注册接受消息,该注册接受消息包括允许的切片的信息、拒绝的切片的信息、第一RA的信息以及第一指示信息,第一指示信息用于指示第二TA支持第一切片,第二TA属于第一RA中的一个,第一切片属于拒绝的切片中的一个。
相应地,终端设备接收来自AMF的注册接受消息。
步骤805,终端设备继续进行其他注册流程,以完成注册。
上述步骤801-805可以参照方法500中的步骤501-505进行理解,在此仅阐述不同之处。在本申请实施例中,和前述图5所示实施例不同的地方主要在于,在方法500中,当终端设备从第一TA移动至第二TA时,终端设备根据第一指示信息向AMF发送第二注册请求消息,第二注册请求消息包括第一切片。而在本实施例中,终端设备直接发起会话建立请求,而跳过了注册流程。
具体地,方法800还包括:
步骤806,终端设备根据第一指示信息,当终端设备位于支持第一切片的第二TA区域内时,若其仍需要接入第一切片(可以根据APP的需求等判断),则发起会话建立请求,将第一TA支持的第一切片添加在会话建立请求中。AMF根据终端设备当前的TA和TA支持的切片情况,不拒绝终端设备的会话建立请求,进行会话建立流程。
步骤807,终端设备因切换(handover)触发TA的改变。
步骤808a,终端设备进入空闲(IDLE)态,因接收到寻呼(paging)消息(寻呼第一RA内的所有TA)而发起服务请求(service request),或者进入步骤808b。
步骤808b,终端设备因业务需求发起服务请求,其中携带需要激活的会话信息等。
步骤809,AMF发现终端设备因步骤807中切换流程触发TA改变,或收到终端的服务请求后对终端设备当前的TA和终端设备会话的切片信息进行验证。若存在会话其切片在当前TA内不支持,则触发该会话的释放流程。
步骤810,进行PDU会话释放流程。
图9是本申请实施例提供的通信方法900的示意性流程图,图9所示实施例可以看作是图5所示实施例的一种变形方式。以下,结合图9说明本申请实施例提供的通信方法900,方法900包括:
步骤901,终端设备在第一跟踪区域TA内向AMF发送第一注册请求消息,第一注册请求消息中携带请求的切片的信息和第一能力指示信息,其中,第一能力指示信息用于指示终端设备是否具备接收前述任一实施例中的第一指示信息的能力。
步骤902,AMF确定允许切片和拒绝的切片。
步骤903,AMF根据允许的切片以及第一能力指示信息的指示,给终端设备分配第一RA或者第二RA。
具体地,当第一能力指示信息指示终端设备具备接收所述第一指示信息的能力时,AMF可以按照前述步骤503、603、703中的方法给终端设备分配第一RA,该第一RA中的至少一个TA能够支持拒绝的切片中的至少一个。而当第一能力指示信息指示终端设备不具备接收所述第一指示信息的能力时,此时AMF给终端设备分配第二RA,第二RA种的任意一个TA可以均不支持拒绝的切片。下面以表3为例进行说明。
表3:
在表3中,AMF确定允许的切片仅包括切片#3,拒绝的切片包括切片#1,切片#2。如果第一能力指示信息指示终端设备具备接收所述第一指示信息的能力时,则按照前述实施例中介绍的方法(详见步骤503的介绍)分配第一RA给终端设备。这是第一RA包括TA#1~TA#5共五个TA。如果第一能力指示信息指示终端设备不具备接收所述第一指示信息的能力时,则给终端设备分配第二RA,第二RA中的每一个TA除了均应当支持切片#3以外,还应当均不支持任意一个拒绝的切片,即不能支持切片#1和切片#2,因此相对于第一RA,在第二RA中应当将TA#2、TA#3和TA#5排除,即第二RA仅包括TA#1和TA#4。
当第一能力指示信息指示终端设备具备接收第一指示信息的能力时,进入步骤904a。
可选地,AMF也可以通过其他方式获取该第一能力指示信息,例如,可以通过终端设备的签约信息获取到该第一能力指示信息,AMF自身可以存储有该签约信息,或者AMF也可以通过从NSSF、UDM等其他网元处获取到该签约信息(第一能力指示信息),本申请对AMF获取第一能力指示信息的方式不作特殊限定。
在步骤904a中,AMF向终端设备发送注册接受消息,注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,第一指示信息用于指示第二跟踪区域TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于拒绝的切片;或者,
第一指示信息用于指示终端设备在第二TA内允许发起对拒绝的切片中的任意一个切片的连接请求,第二TA属于第一RA并支持拒绝的切片中的至少一个切片,拒绝的切片包括第一切片;或者,
第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系,第一切片属于所述拒绝的切片,第一RA包括第二TA。
当终端设备接收到包含有第一指示信息的注册接受消息时,可以继续按照前述方法500~方法800中的相关步骤,向AMF发送第二注册请求消息,第二注册请求消息包括第一切片的信息。
当第一能力指示信息指示终端设备不具备接收第一指示信息的能力时,进入步骤904b。
在步骤904b中,AMF向终端设备发送注册接受消息,注册接受消息包括拒绝的切片的信息以及第二RA的信息,第二RA中的任意一个TA均不支持拒绝的切片。
此时,当终端设备接收到不包含第一指示信息的注册接受消息、并且终端设备移动至第二TA时,此时由于第二TA不属于当前的RA,因此可能因为终端设备移动到原来的RA以外的TA中,引起了移动性注册更新,因此需要再次向核心网发起新的
注册流程。
上文结合图1至图9详细描述了本申请实施例的通信方法,下面结合图10至图13,详细描述本申请实施例的装置。应理解,图10至图13所示的装置能够实现图5-图9所示的方法流程中的一个或者多个的步骤。为避免重复,在此不再详细赘述。
图10是本申请实施例提供的终端设备1000的示意性框图。如图10所示,终端设备1000包括:发送模块1010和接收模块1020。
发送模块1010,用于当终端设备1000在第一跟踪区域TA内时,向核心网设备发送第一注册请求消息;
接收模块1020,用于接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;
所述发送模块1010,还用于当所述终端设备1000从所述第一TA移动至所述第二TA时,根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片。
可选地,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识。
可选地,所述第一指示信息包括多个TA对所述拒绝的切片的支持信息,所述多个TA中的每一个TA均属于所述第一RA并支持所述拒绝的切片中的至少一个切片,所述第二TA为所述多个TA中的任意一个。
可选地,所述接收模块接收来自所述核心网设备的注册接受消息之前,所述发送模块,还用于向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
可选地,所述第一能力指示信息携带于所述第一注册请求消息中。
在其他实施方式中,发送模块1010,用于当所述终端设备1000在第一跟踪区域TA内向核心网设备发送第一注册请求消息;
接收模块1020,用于接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示所述终端设备1000在第二TA内允许发起对所述拒绝的切片中的任意一个切片的连接请求,所述第二TA属于所述第一RA并支持所述拒绝的切片中的至少一个切片,所述拒绝的切片包括第一切片;
所述发送模块1010还用于,当所述终端设备1000从所述第一TA移动至所述第二TA时,根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片。
可选地,所述第一指示信息包括所述第二TA的标识。
可选地,所述第一指示信息用于指示所述终端设备在TA集合中的任一个TA内均允许发起对所述拒绝的切片中的任一个切片的连接请求,所述TA集合中的每一个TA均支持所述拒绝的切片中的至少一个切片,所述第二TA为所述TA集合中的任意一个。
可选地,所述接收模块接收来自所述核心网设备的注册接受消息之前,所述发送
模块,还用于向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
可选地,所述第一能力指示信息携带于所述第一注册请求消息中。
在其他实施方式中,
发送模块1010,用于当所述终端设备1000在第一跟踪区域TA内时,向核心网设备发送第一注册请求消息;
接收模块1020,用于接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系,所述第一切片属于所述拒绝的切片,所述第一RA包括第二TA;
所述接收模块1020还用于,通过所述第二TA的广播消息接收到所述第一NSASG的信息;
所述发送模块1010还用于,在所述终端设备根据所述第一指示信息驻留到所述第二TA时,向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片。
可选地,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
可选地,所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
可选地,所述接收模块接收来自所述核心网设备的注册接受消息之前,所述发送模块,还用于向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
可选地,所述第一能力指示信息携带于所述第一注册请求消息中。
在一种可能的实现方式中,上述终端设备1000可以为下图中的终端设备1100,其中发送模块1010和接收模块1020的功能可以通过终端设备的收发器1101(即控制电路与天线一起)实现。下文结合图11介绍本申请实施例的终端设备1100的结构。
图11是本申请实施例的一种终端设备1100的结构示意图。该终端设备1100可适用于图1所示出的系统中,执行上述方法实施例中终端设备(UE)的功能。为了便于说明,图11仅示出了终端设备的主要部件。如图11所示,终端设备1100包括处理器1102、存储器、控制电路、天线以及输入输出装置。处理器1102主要用于对通信协议以及通信数据进行处理,以及对整个终端设备进行控制,执行软件程序,处理软件程序的数据,例如用于支持终端设备执行上述方法实施例中所描述的动作。存储器主要用于存储软件程序和数据。控制电路主要用于基带信号与射频信号的转换以及对射频信号的处理。控制电路和天线一起也可以叫做收发器1101,主要用于收发电磁波形式的射频信号。输入输出装置,例如触摸屏、显示屏,键盘等主要用于接收用户输入的数据以及对用户输出数据。
当终端设备开机后,处理器1102可以读取存储单元中的软件程序,解释并执行软件程序的指令,处理软件程序的数据。当需要通过无线发送数据时,处理器1102对待发送的数据进行基带处理后,输出基带信号至射频电路,射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时,
射频电路通过天线接收到射频信号,将射频信号转换为基带信号,并将基带信号输出至处理器,处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解,为了便于说明,图11仅示出了一个存储器和一个处理器。在实际的终端设备中,可以存在多个处理器和多个存储器。存储器也可以称为存储介质或者存储设备等,本申请实施例对此不做限定。
作为一种可选的实现方式,处理器可以包括基带处理器和中央处理器,基带处理器主要用于对通信协议以及通信数据进行处理,中央处理器主要用于对整个终端设备进行控制,执行软件程序,处理软件程序的数据。图11中的处理器可以集成基带处理器和中央处理器的功能,本领域技术人员可以理解,基带处理器和中央处理器也可以是各自独立的处理器,通过总线等技术互联。本领域技术人员可以理解,终端设备可以包括多个基带处理器以适应不同的网络制式,终端设备可以包括多个中央处理器以增强其处理能力,终端设备的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中,也可以以软件程序的形式存储在存储单元中,由处理器执行软件程序以实现基带处理功能。
图12是本申请实施例提供的核心网设备1200的示意性框图。图12所示的核心网设备1200包括接收模块1210和发送模块1220。
接收模块1210,用于接收来自终端设备的第一注册请求消息;
发送模块1220,用于向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,
所述第一指示信息用于指示第二TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;或者,
所述第一指示信息用于指示所述终端设备在第二TA内允许发起对所述拒绝的切片中的任意一个切片的连接请求,所述第二TA属于所述第一RA并支持所述拒绝的切片中的至少一个切片,所述拒绝的切片包括第一切片;或者,
所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系,所述第一切片属于所述拒绝的切片,所述第一RA包括第二TA;
所述接收模块1210还用于,接收来自所述终端设备的第二注册请求消息,所述第二注册请求消息包括所述第一切片。
可选地,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识;或者,所述第一指示信息包括所述第二TA的标识;或者,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
可选地,所述第一指示信息包括多个TA对所述拒绝的切片的支持信息,所述多个TA中的每一个TA均属于所述第一RA并支持拒绝的切片中的至少一个切片,所述第二TA为所述多个TA中的任意一个;或者,
所述第一指示信息用于指示所述终端设备在TA集合中的任一个TA内均允许发起对所述拒绝的切片中的任一个切片的连接请求,所述TA集合中的每一个TA均支持所述拒绝的切片中的至少一个切片,所述第二TA为所述TA集合中的任意一个;
或者,
所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
可选地,所述接收模块1210还用于,接收来自所述终端设备的第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力;
所述发送模块1220具体用于,根据所述第一能力指示信息向所述终端设备发送所述注册接受消息。
可选地,所述第一能力指示信息携带于所述第一注册请求消息中。
在其他实现方式中,
接收模块1210,用于接收来自终端设备的第一注册请求消息,所述第一注册请求消息包括第一能力指示信息,所述第一能力指示信息用于指示所述终端设备是否具备接收第一指示信息的能力;
发送模块1220,当所述第一能力指示信息指示终端设备具备接收所述第一指示信息的能力时,用于向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二跟踪区域TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;或者,
所述第一指示信息用于指示所述终端设备在第二TA内允许发起对所述拒绝的切片中的任意一个切片的连接请求,所述第二TA属于所述第一RA并支持所述拒绝的切片中的至少一个切片,所述拒绝的切片包括第一切片;或者,
所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系,所述第一切片属于所述拒绝的切片,所述第一RA包括第二TA;
当所述第一能力指示信息指示终端设备不具备接收所述第一指示信息的能力时,所述发送模块用于向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息以及第二RA的信息,所述第二RA中的任意一个TA均不支持所述拒绝的切片。
可选地,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识;或者,所述第一指示信息包括所述第二TA的标识;或者,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
可选地,所述第一指示信息包括多个TA对拒绝的切片的支持信息,所述多个TA中的每一个TA均属于所述第一RA并支持拒绝的切片中的至少一个切片,所述第二TA为所述多个TA中的任意一个;或者,
所述第一指示信息用于指示所述终端设备在TA集合中的任一个TA内均允许发起对所述拒绝的切片中的任一个切片的连接请求,所述TA集合中的每一个TA均支持所述拒绝的切片中的至少一个切片,所述第二TA为所述TA集合中的任意一个;或者,
所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
图13是本申请实施例提供的核心网设备1300的结构示意图。如图13所示,该核
心网设备1300包括:处理器1310、存储器1320和通信接口1330。其中,存储器1320中存储有指令,处理器1310用于执行存储器1320中的指令,当该指令被执行时,该处理器1310用于执行上述任一个方法实施例提供的方法,处理器1310还用于控制通信接口1330与外界进行通信。
进一步地,该处理器1310、存储器1320和通信接口1330可以通过内部连接通路互相通信,传递控制和/或数据信号。
进一步地,该存储器1320可以集成在处理器1310中,也可以与处理器1310分开设置。
具体地,核心网设备1300可以用于执行图5-图9中的通信方法中的各个步骤,该核心网设备1300可以包括图12中用于执行前述通信方法的各个模块。并且,该核心网设备1300中的各模块和上述其他操作和/或功能分别为了实现图5-图9中通信方法的相应流程。各模块执行上述相应步骤的具体过程在方法中已经详细说明,为了简洁,在此不再赘述。
应理解,在本申请实施例中的处理器可以是中央处理单元(Central Processing Unit,CPU),该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现成可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的随机存取存储器(random access memory,RAM)可用,例如静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。
根据本申请实施例提供的方法,本申请还提供一种计算机程序产品,该计算机程序产品包括:计算机程序代码,当该计算机程序代码在计算机上运行时,使得该计算机执行图5-图9所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法,本申请还提供一种计算机可读介质,该计算机可读介质存储有程序代码,当该程序代码在计算机上运行时,使得该计算机执行图5-图9所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法,本申请还提供一种系统,其包括前述的一个或多个终端设备、一个或多个接入网设备、一个或者多个核心网设备。
上述实施例,可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时,上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质。半导体介质可以是固态硬盘。
为了便于理解,下文中对本申请介绍方案的过程中涉及的名词进行说明。
在本申请实施例中,“指示”可以包括直接指示和间接指示,也可以包括显式指示和隐式指示。将某一信息(如前文中的“指示信息”)所指示的信息称为待指示信息,则具体实现过程中,对待指示信息进行指示的方式有很多种,例如但不限于,可以直接指示待指示信息,如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息,其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分,而待指示信息的其他部分则是已知的或者提前约定的。例如,还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示,从而在一定程度上降低指示开销。
在本申请实施例中,“第一”、“第二”以及各种数字编号仅为描述方便进行的区分,并不用来限制本申请实施例的范围。例如,区分不同的指示信息等。
本申请实施例中涉及的“通信协议”可以是指通信领域的标准协议,例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议,本申请对此不做限定。
本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
本申请中,“至少一个”是指一个或者多个,“多个”是指两个或两个以上。“以下至少一项(个)”或其类似表达,是指的这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,a,b,或c中的至少一项(个),可以表示:a,b,c,a-b,a-c,b-c,或a-b-c,其中a,b,c可以是单个,也可以是多个。
在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专
业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。
Claims (30)
- 一种通信方法,其特征在于,包括:终端设备在第一跟踪区域TA内向核心网设备发送第一注册请求消息;所述终端设备接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;当所述终端设备从所述第一TA移动至所述第二TA时,所述终端设备根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
- 根据权利要求1所述的通信方法,其特征在于,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识。
- 根据权利要求1或2所述的通信方法,其特征在于,所述第一指示信息包括多个TA对所述拒绝的切片的支持信息,所示支持信息用于指示所述多个TA中的每一个TA支持所述拒绝的切片中的至少一个切片,或者用于指示所述多个TA中的每一个TA所支持的所述拒绝的切片中的切片,所述多个TA中的每一个TA均属于所述第一RA,所述多个TA包括所述第二TA。
- 根据权利要求1-3中任一项所述的通信方法,其特征在于,所述终端设备接收来自所述核心网设备的注册接受消息之前,所述方法还包括:所述终端设备向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
- 根据权利要求4所述的通信方法,其特征在于,所述第一能力指示信息携带于所述第一注册请求消息中。
- 一种通信方法,其特征在于,包括:终端设备在第一跟踪区域TA内向核心网设备发送第一注册请求消息;所述终端设备接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示允许所述终端设备在第二TA内发起对所述拒绝的切片中的任意一个切片的连接请求,所述拒绝的切片包括第一切片;当所述终端设备从所述第一TA移动至所述第二TA时,所述终端设备根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
- 根据权利要求6所述的通信方法,其特征在于,所述第一指示信息包括所述第二TA的标识。
- 根据权利要求6或7所述的通信方法,其特征在于,所述第一指示信息包括TA集合,所述TA集合包括允许所述终端设备发起对所述拒绝的切片中的任意一个切片的连接请求的TA的标识,所述TA集合包括所述第二TA标识。
- 根据权利要求6-8中任一项所述的通信方法,其特征在于,所述终端设备接收来自所述核心网设备的注册接受消息之前,所述方法还包括:所述终端设备向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
- 根据权利要求9所述的通信方法,其特征在于,所述第一能力指示信息携带于所述第一注册请求消息中。
- 一种通信方法,其特征在于,包括:终端设备在第一跟踪区域TA内向核心网设备发送第一注册请求消息;所述终端设备接收来自所述核心网设备的注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系;所述终端设备通过所述第一RA中的第二TA的广播消息接收所述第一NSASG的信息;所述终端设备驻留到所述第二TA,并且根据所述第一指示信息向所述核心网设备发送第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
- 根据权利要求11所述的通信方法,其特征在于,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
- 根据权利要求11或12所述的通信方法,其特征在于,所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
- 根据权利要求11-13中任一项所述的通信方法,其特征在于,所述终端设备接收来自所述核心网设备的注册接受消息之前,所述方法还包括:所述终端设备向所述核心网设备发送第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力。
- 根据权利要求14所述的通信方法,其特征在于,所述第一能力指示信息携带于所述第一注册请求消息中。
- 一种通信方法,其特征在于,包括:核心网设备接收来自终端设备的第一注册请求消息;所述核心网设备向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;或者,所述第一指示信息用于指示允许所述终端设备在第二TA内发起对所述拒绝的切片中的任意一个切片的连接请求,所述拒绝的切片包括第一切片;或者,所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系;所述核心网设备接收来自所述终端设备的第二注册请求消息,所述第二注册请求消息包括所述第一切片的信息。
- 根据权利要求16所述的通信方法,其特征在于,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识;或者,所述第一指示信息包括所述第二TA的标识;或者,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
- 根据权利要求16或17所述的通信方法,其特征在于,所述第一指示信息包括多个TA对拒绝的切片的支持信息,所示支持信息用于指示所述多个TA中的每一个TA支持所述拒绝的切片中的至少一个切片,或者用于指示所述多个TA中的每一个TA所支持的所述拒绝的切片中的切片,所述多个TA中的每一个TA均属于所述第一RA,所述多个TA包括所述第二TA;或者,所述第一指示信息包括TA集合,所述TA集合包括允许所述终端设备发起对所述拒绝的切片中的任意一个切片的连接请求的TA的标识,所述TA集合包括所述第二TA的标识;或者,所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
- 根据权利要求16-18中任一项所述的通信方法,其特征在于,所述方法还包括:所述核心网设备接收来自所述终端设备的第一能力指示信息,所述第一能力指示信息用于指示所述终端设备具备接收所述第一指示信息的能力;所述核心网设备向所述终端设备发送注册接受消息包括:所述核心网设备根据所述第一能力指示信息向所述终端设备发送所述注册接受消息。
- 根据权利要求19所述的通信方法,其特征在于,所述第一能力指示信息携带于所述第一注册请求消息中。
- 根据权利要求16-19中任一项所述的通信方法,其特征在于,所述核心网设备向所述终端设备发送注册接受消息之前,所述方法还包括:所述核心网设备确定所述第二TA属于所述第一RA并支持所述拒绝的切片中的至少一个切片。
- 一种通信方法,其特征在于,包括:核心网设备接收来自终端设备的第一注册请求消息;所述核心网设备获取第一能力指示信息,所述第一能力指示信息用于指示所述终端设备是否具备接收第一指示信息的能力;当所述第一能力指示信息指示终端设备具备接收所述第一指示信息的能力时,所述核心网设备向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切片的信息、第一注册区域RA的信息以及第一指示信息,所述第一指示信息用于指示第二跟踪区域TA支持第一切片,所述第二TA属于所述第一RA,所述第一切片属于所述拒绝的切片;或者,所述第一指示信息用于指示允许所述终端设备在第二TA内发起对所述拒绝的切片中的任意一个切片的连接请求,所述拒绝的切片包括第一切片;或者,所述第一指示信息用于指示第一切片与第一网络切片接入层群组NSASG之间具有映射关系;当所述第一能力指示信息指示终端设备不具备接收所述第一指示信息的能力时,所述核心网设备向所述终端设备发送注册接受消息,所述注册接受消息包括拒绝的切 片的信息以及第二RA的信息,所述第二RA中的任意一个TA均不支持所述拒绝的切片。
- 根据权利要求22所述的通信方法,其特征在于,所述第一指示信息包括所述第二TA的标识和所述第一切片的标识;或者,所述第一指示信息包括所述第二TA的标识;或者,所述第一指示信息包括所述第一切片的标识和所述第一NSASG的标识。
- 根据权利要求22或23所述的通信方法,其特征在于,所述第一指示信息包括多个TA对拒绝的切片的支持信息,所示支持信息用于指示所述多个TA中的每一个TA支持所述拒绝的切片中的至少一个切片,或者用于指示所述多个TA中的每一个TA所支持的所述拒绝的切片中的切片,所述多个TA中的每一个TA均属于所述第一RA,所述多个TA包括所述第二TA;或者,所述第一指示信息包括TA集合,所述TA集合包括允许所述终端设备发起对所述拒绝的切片中的任意一个切片的连接请求的TA的标识,所述TA集合包括所述第二TA的标识;或者,所述第一指示信息用于指示所述拒绝的切片中的多个切片与NSASG的映射关系,所述第一切片为所述多个切片中的任一个。
- 根据权利要求22-24中任一项所述的通信方法,其特征在于,所述第一能力指示信息携带于所述第一注册请求消息中。
- 一种终端设备,其特征在于,包括至少一个处理器,所述至少一个处理器用于与存储器耦合,读取并执行所述存储器中的指令,以实现如权利要求1至15中任一项所述的方法。
- 一种核心网设备,其特征在于,包括至少一个处理器,所述至少一个处理器用于与存储器耦合,读取并执行所述存储器中的指令,以实现如权利要求16至24中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有计算机程序,当所述计算机程序在计算机上运行时,使得所述计算机执行如权利要求1至24中任意一项所述的方法。
- 一种计算机程序产品,其特征在于,包括:计算机程序代码,当所述计算机程序代码在计算机上运行时,使得所述计算机执行如权利要求1至24中任意一项所述的方法。
- 一种通信系统,其特征在于,包括如权利要求26所述的终端设备和/或如权利要求27所述的核心网设备。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210329805.5 | 2022-03-28 | ||
CN202210329805.5A CN116867054A (zh) | 2022-03-28 | 2022-03-28 | 通信方法及终端设备、核心网设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023185295A1 true WO2023185295A1 (zh) | 2023-10-05 |
Family
ID=88199111
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2023/076228 WO2023185295A1 (zh) | 2022-03-28 | 2023-02-15 | 通信方法及终端设备、核心网设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN116867054A (zh) |
WO (1) | WO2023185295A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111052818A (zh) * | 2017-09-05 | 2020-04-21 | 华为技术有限公司 | 网络实体、用户设备和网络切片的控制和使用方法 |
CN113411815A (zh) * | 2020-03-16 | 2021-09-17 | 华为技术有限公司 | 一种接入网络切片的方法及装置 |
WO2021204343A1 (en) * | 2020-04-06 | 2021-10-14 | Nokia Technologies Oy | Communication system |
CN114208272A (zh) * | 2019-07-31 | 2022-03-18 | 高通股份有限公司 | 网络切片可用性检查和指示 |
-
2022
- 2022-03-28 CN CN202210329805.5A patent/CN116867054A/zh active Pending
-
2023
- 2023-02-15 WO PCT/CN2023/076228 patent/WO2023185295A1/zh unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111052818A (zh) * | 2017-09-05 | 2020-04-21 | 华为技术有限公司 | 网络实体、用户设备和网络切片的控制和使用方法 |
CN114208272A (zh) * | 2019-07-31 | 2022-03-18 | 高通股份有限公司 | 网络切片可用性检查和指示 |
CN113411815A (zh) * | 2020-03-16 | 2021-09-17 | 华为技术有限公司 | 一种接入网络切片的方法及装置 |
WO2021204343A1 (en) * | 2020-04-06 | 2021-10-14 | Nokia Technologies Oy | Communication system |
Non-Patent Citations (1)
Title |
---|
HUAWEI, HISILICON: "Enabling Network Slice Acess stratum group", 3GPP DRAFT; S2-2200281, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20220214 - 20220225, 28 January 2022 (2022-01-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052124523 * |
Also Published As
Publication number | Publication date |
---|---|
CN116867054A (zh) | 2023-10-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20220191100A1 (en) | Method and device for providing connectivity to terminal in order to use edge computing service | |
US11528761B2 (en) | Communication method and communications apparatus | |
US11172405B2 (en) | Method for checking change in wireless connection type of terminal in third-party application server | |
EP3668054A1 (en) | Data transmission method, device and system | |
CN114651482A (zh) | 在无线通信系统中控制网络切片的方法和装置 | |
WO2023280121A1 (zh) | 一种获取边缘服务的方法和装置 | |
EP3823332B1 (en) | Communication method and apparatus | |
WO2020221223A1 (zh) | 通信方法、装置和系统 | |
WO2021203827A1 (zh) | 一种通信的方法及装置 | |
JP2021510030A (ja) | 無線通信方法及び装置 | |
WO2022001318A1 (zh) | 通信方法和装置 | |
EP3860176A1 (en) | Method, apparatus, and system for obtaining capability information of terminal | |
WO2021068830A1 (zh) | 用于多播传输的方法和装置 | |
US20230388908A1 (en) | Network slice-based communication method and apparatus | |
CN114339821A (zh) | 用于分布式nwdaf之间的机器学习模型共享的方法和装置 | |
JP2023524903A (ja) | 通信方法および装置 | |
EP4152881A1 (en) | Communication method and communication apparatus | |
US20230362748A1 (en) | Wireless communication method, communication apparatus, and communication system | |
WO2023080057A1 (en) | Method of access and mobility management function (amf) apparatus, method of next generation-radio access network (ng-ran) node, method of user equipment (ue), method of master node (mn), amf apparatus, ng-ran node, ue, and mn | |
US20220377547A1 (en) | Wireless communication method, terminal device and network element | |
CN114501612B (zh) | 一种资源分配方法及终端、网络设备、存储介质 | |
WO2023185295A1 (zh) | 通信方法及终端设备、核心网设备 | |
WO2023185561A1 (zh) | 通信方法和通信装置 | |
WO2023116556A1 (zh) | 会话切换的方法和装置 | |
EP4398610A1 (en) | Communication method and apparatus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 23777674 Country of ref document: EP Kind code of ref document: A1 |