WO2022160090A1 - 信息发送方法和装置、信息接收方法和装置 - Google Patents

信息发送方法和装置、信息接收方法和装置 Download PDF

Info

Publication number
WO2022160090A1
WO2022160090A1 PCT/CN2021/073757 CN2021073757W WO2022160090A1 WO 2022160090 A1 WO2022160090 A1 WO 2022160090A1 CN 2021073757 W CN2021073757 W CN 2021073757W WO 2022160090 A1 WO2022160090 A1 WO 2022160090A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice
base station
information
terminal
message
Prior art date
Application number
PCT/CN2021/073757
Other languages
English (en)
French (fr)
Inventor
刘晓菲
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202180000291.2A priority Critical patent/CN112913279B/zh
Priority to PCT/CN2021/073757 priority patent/WO2022160090A1/zh
Publication of WO2022160090A1 publication Critical patent/WO2022160090A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to an information sending method and apparatus, an information receiving method and apparatus, an electronic device and a computer-readable storage medium.
  • Network slicing is to divide a physical network into multiple virtual logical networks to flexibly provide differentiated services for different users.
  • each network slice has a unique corresponding slice identifier, and the traffic of different slices can be processed by different PDU (Protocol Data Unit) sessions.
  • PDU Protocol Data Unit
  • the terminal determines the corresponding PDU session for the service, and determines the slice information corresponding to the PDU session. Then, the terminal sends non-access stratum NAS (Non-access stratum) information to the core network, and the NAS message carries the corresponding slice information, and requests to obtain the relevant resources of the PDU session.
  • NAS Non-access stratum
  • the core network may instruct the access network RAN to allocate corresponding resources for the PDU session.
  • the RAN may refuse to allocate resources for the PDU session, thereby causing the terminal's request to fail.
  • the embodiments of the present disclosure propose an information sending method and apparatus, and an information receiving method and apparatus, so as to solve the technical problems in the related art.
  • a method for sending information is provided, which is applied to a terminal, and the method includes:
  • the slice information is used for the first base station to determine whether to hand over the terminal to the second base station that supports the slice.
  • an apparatus for sending information which is applied to a terminal, and the apparatus includes:
  • an information determination module configured to determine the slice information of the slice corresponding to the initiated service
  • an information sending module configured to send the slice information to the first base station
  • the slice information is used for the first base station to determine whether to hand over the terminal to the second base station that supports the slice.
  • a method for receiving information is provided, which is applied to a first base station, and the method includes:
  • Whether to hand over the terminal to the second base station supporting the slice is determined according to the slice information.
  • a receiving apparatus which is applied to a first base station, and the apparatus includes:
  • an information receiving module configured to receive slice information of a slice corresponding to a service initiated by the terminal and sent by the terminal;
  • a handover module configured to determine whether to handover the terminal to a second base station supporting the slice according to the slice information.
  • an electronic device including:
  • memory for storing processor-executable instructions
  • the processor is configured to implement the method of the first aspect and/or the second aspect.
  • a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the steps in the method of the first aspect and/or the second aspect.
  • the terminal sends slice information of the slice to the currently accessed first base station, and the first base station can determine whether to switch the terminal to the second base station that supports or preferentially supports the slice according to the slice information. Therefore, even if the first base station does not support the slice, the terminal can be handed over to the second base station to ensure that the terminal successfully establishes a PDU session and communicates based on the PDU session in a timely manner.
  • FIG. 1 is a schematic flowchart of a method for sending information according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic flowchart of another method for sending information according to an embodiment of the present disclosure.
  • FIG. 3 is a schematic flowchart of another method for sending information according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart of a method for receiving information according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart of another method for receiving information according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of another method for receiving information according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart of another method for receiving information according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic block diagram of an information sending apparatus according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic block diagram of an information receiving apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic block diagram of an apparatus for receiving information according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic block diagram of an apparatus for sending information according to an embodiment of the present disclosure.
  • the corresponding relationship between services and network slices may be preset in the terminal.
  • the terminal may record the corresponding relationship between services and network slices through a URSP (UE Route Selection Policy, UE routing policy).
  • URSP UE Route Selection Policy, UE routing policy
  • one or more URSP rules may be included, and each URSP rule may include rule priority, service descriptor Traffic Descriptor, and RSD (Route selection descriptor, route selection descriptor) list list, etc., wherein, in the RSD list It may include network slice identification, such as one or more single network slice selection assistance information S-NSSAI.
  • the terminal can determine the Traffic Descriptor of the service, and then search the preset URSP for a matching slice identifier. For the found slice identifier, if the slice identifier has a corresponding existing PDU session, the service is associated with the existing PDU session; if the slice identifier does not have a corresponding existing PDU session, a new PDU session is established .
  • the terminal may send a NAS message to the network to request to establish a PDU session, modify a PDU session, or activate a PDU session.
  • the terminal may send a NAS message to the core network through the current serving base station, and the NAS message carries slice information corresponding to the PDU session. If the core network accepts the establishment, modification or activation of the PDU session, the core network may instruct the base station to allocate resources for the PDU session.
  • the core network will set the slices supported by all base stations covering the terminal to the slices that the terminal is allowed to use, for example
  • the set of slice identifiers S-NSSAI supported by all cells covering the terminal may be set as the slice identifier Allowed NSSAI that the terminal is allowed to use.
  • the slices supported by different base stations may be different. Taking base station 1 supporting slice 1 and base station 2 supporting slice 2 as an example, both slice 1 and slice 2 are slices that are allowed to be used by the terminal.
  • the terminal When the terminal is located in the overlapping coverage of base station 1 and base station 2, and base station 1 is the serving base station of the terminal, when the terminal initiates a service, if the PDU session corresponding to slice 2 needs to be used, the terminal sends a NAS to the core network through the currently accessed base station 1 The message requests resource allocation for the PDU session. After receiving the NAS message, the core network can instruct the base station 1 to allocate relevant resources to the terminal. However, if base station 1 supports slice 1 but does not support slice 2, base station 1 will refuse to allocate resources for the PDU session. Therefore, the request of the terminal to allocate resources for the PDU session fails.
  • the slices supported by different base stations may also be the same, but the slices preferably supported by different base stations are different.
  • the base station can provide services with better performance; for slices that are not preferred to support, there may be problems such as poor signal quality. Therefore, if the base station establishes the communication of the slice at the base station that does not preferentially support the slice, there may be a problem of poor communication quality and poor user experience.
  • an embodiment of the present disclosure proposes a method for sending and receiving information.
  • the terminal sends the slice information of the slice to the currently accessed first base station, and the first base station can determine the slice information according to the slice information. Whether to switch the terminal to a second base station that supports or preferentially supports the slice. Therefore, even if the first base station does not support the slice, the terminal can be handed over to the second base station to ensure that the terminal successfully establishes a PDU session, which improves processing efficiency.
  • FIG. 1 is a schematic flowchart of a method for sending information according to an embodiment of the present disclosure.
  • the information sending method shown in this embodiment may be applicable to terminals, and the terminals include but are not limited to electronic devices such as mobile phones, tablet computers, wearable devices, sensors, and Internet of Things devices.
  • the terminal may communicate with a base station as a user equipment, and the base station includes but is not limited to a 4G base station, a 5G base station, and a 6G base station.
  • the base station may be the first base station and/or the first base station in any subsequent embodiment. or the second base station.
  • the information sending method may include the following steps:
  • step S101 the slice information of the slice corresponding to the initiated service is determined.
  • the terminal may determine the corresponding PDU session for the service to be initiated, for example, may be establishing, modifying or activating the PDU session, and determining the slice information of the slice corresponding to the PDU session.
  • the slice information may include a slice identifier, for example, may be one or more of the following slice identifiers: single network slice selection assistance information S-NSSAI of the slice, slice/service type SST of the slice, The slice index slice index, or the access type defined by the operator corresponding to the slice.
  • the slice information may also be other information, as long as it is information that can uniquely indicate a slice, which is merely illustrative and not limiting.
  • step S102 the slice information is sent to the first base station.
  • the slice information is used for the first base station to determine whether to hand over the terminal to the second base station that supports the slice.
  • the terminal sends the slice information of the slice to the currently accessed first base station, so that the first base station can determine whether to switch the terminal to the second base station supporting the slice according to the slice information. Therefore, even if the first base station does not support the slice, the terminal can be handed over to the second base station to ensure that the terminal successfully establishes a PDU session and communicates based on the PDU session in a timely manner.
  • the NAS message sent by the terminal to the core network through the first base station may include slice information, but since the first base station will not parse the NAS message, the terminal also needs to send the AS message to the first base station in the AS message. It carries slice information.
  • the terminal may carry the slice information in the AS message for sending the NAS message.
  • the AS message may be a ULinformationtransfer message
  • the terminal may carry the slice information in the ULinformationtransfer message.
  • the non-access stratum NAS message may be a message requesting the core network to allocate resources related to a PDU session, such as a request for establishing, modifying or activating a PDU session.
  • the terminal may send the NAS message to the first base station, and also include the slice information in the AS message (for example, the UL information transfer message) carrying the NAS message. Therefore, the terminal sends a piece of information to the first base station, which can not only forward the NAS message to the core network through the first base station, but also enable the first base station to know the slice information corresponding to the NAS message through the AS message, and the information transmission efficiency is high and saves money. communication resources.
  • the first base station may determine whether to hand over the terminal to the second base station that supports the slice.
  • the first base station may parse and perform subsequent processing on the AS message. For example, the first base station may parse and obtain slice information from the AS message, so as to determine whether to hand over the terminal to the second base station that supports the slice according to the slice information.
  • the slice information is used for the first base station to hand over the terminal to the second base station if it is determined that the first base station does not support the slice. Based on this, in one embodiment, in response to determining that the slice is not supported according to the slice information, the first base station switches the terminal to the second base station.
  • the slice information is used for the first base station to switch the terminal to a second base station that preferentially supports the slice if it is determined that the first base station does not preferentially support the slice. Based on this, in one embodiment, in response to determining that the slice is not preferentially supported according to the slice information, the terminal is handed over to a second base station that preferentially supports the slice.
  • the NAS layer determines the slice information corresponding to the service, and the terminal needs to send the slice information to the first base station through the AS layer.
  • the terminal may use the method of FIG. 2 to determine slice information.
  • FIG. 2 is a schematic flowchart of another method for sending information according to an embodiment of the present disclosure.
  • the slice information of the slice corresponding to the determined service initiated includes:
  • step S201 in response to the service to be initiated, the slice information of the slice corresponding to the service is determined through the non-access stratum.
  • the NAS layer in the terminal may match the URSP rules to determine the slice information of the slice corresponding to the service.
  • step S202 the slice information is sent to the access stratum through the non-access stratum.
  • the AS layer in the terminal may acquire the slice information from the NAS layer. Therefore, the slice information can be carried in the AS message, and the AS message can be sent to the first base station.
  • the NAS layer in the terminal, can first determine the slice information of the slice corresponding to the service to be initiated, and then generate a NAS message including the slice information, and then the AS layer can obtain the NAS message and obtain the NAS message slice information in . Therefore, the AS layer can carry the slice information in the AS message, and send the NAS message through the AS message carrying the slice information.
  • the terminal may or may not have the ability to obtain information about the supported slices of the first base station.
  • the capability information of the first base station about supporting slices may include whether the first base station supports slices.
  • the information about the capability of the first base station about supporting slices may include the slices that the first base station prefers to support, for example, may be the priorities of multiple supported slices, so that the terminal can determine the slices that the first base station prefers to support according to the priorities .
  • the terminal will also send the NAS message to the first base station.
  • the slice information of the slice needs to be sent.
  • the terminal may first determine whether the first base station supports or preferably supports the slice. In one embodiment, the terminal sends the slice information to the first base station in response to determining that the first base station does not support the slice or that the first base station does not preferentially support the slice. In response to the first base station supporting or determining that the first base station preferably supports the slice, the terminal does not need to send the slice information to the first base station.
  • the terminal when initiating a service, the terminal first determines the slice corresponding to the service, and then determines whether the first base station supports the slice or whether it is preferred to support the slice. If it is determined that the first base station does not support the slice or does not prefer to support the slice, the terminal also sends slice information to the first base station when sending the NAS message for requesting the service-related resources to the core network through the first base station. For example, the terminal may carry slice information in the AS message used to send the NAS message. Therefore, the terminal only sends one message, which can not only forward the NAS message to the core network through the first base station, but also enable the first base station to know the slice corresponding to the NAS message through the AS message, and the communication efficiency is high.
  • the terminal if the terminal has the ability to obtain the information about the supported slices of the first base station, it does not need to send slice information to the first base station in all sent NAS messages, but determines that the first base station does not support or is not preferred Slice information is sent when slicing is supported. In this way, the terminal can avoid sending useless information and improve the information transmission efficiency.
  • the terminal may acquire the capability information of the first base station about supporting slices in various ways. The following takes FIG. 3 as an example for illustrative description.
  • FIG. 3 is a schematic flowchart of another method for sending information according to an embodiment of the present disclosure. As shown in Figure 3, the method further includes:
  • step S301 a system message SI or a radio resource control message RRC sent by the first base station is received, wherein the system message or the radio resource control message carries the capability information of the first base station about supporting slices .
  • the information about the capability of supporting slices may include slices supported by the first base station, or slices that are preferably supported by the first base station, or may also include slices supported by the first base station and slices supported by the first base station. Slice priority, etc.
  • the first base station may carry the capability information of the first base station about supporting slices in the sent system message SI.
  • the first base station may carry the information about the capability of supporting slices in a system message block SIB sent by broadcast.
  • the first base station may carry the capability information of the first base station about supporting slices in the RRC message sent to the terminal. For example, after establishing a connection with the terminal, the first base station may send the information about the capability of supporting slices through an RRC message.
  • the terminal may also not acquire the capability information of the first base station about supporting slices from the first base station. For example, before accessing the first base station, the terminal may obtain the capability information of the first base station about supporting slices from the original base station that was accessed, for example, it may be obtained from the RRC Release message of the original base station. For example, the terminal may also obtain information about the capability of the first base station supporting slices from the core network through the NAS layer. For example, when the core network configures Allowed NSSAI for the terminal, it may also indicate the base station corresponding to each slice, for example, for each slice , which can indicate the base station that supports the slice, or the base station that supports the slice preferentially, and so on.
  • the terminal may also obtain it through other methods, which is merely an exemplary description and not a limitation.
  • step S302 it is determined whether the first base station supports or preferentially supports the slice according to the capability information of the first base station about supporting the slice.
  • the terminal may determine whether the first base station supports the slices; if If the capability information includes the slice that is preferably supported by the first base station, the terminal may determine whether the first base station preferentially supports the slice.
  • the terminal may acquire capability information of the first base station about supporting slices in various manners, so as to determine whether the first base station supports the slices according to the capability information. Therefore, the terminal does not need to always send slice information to the first base station when sending a NAS message, but sends slice information when it is determined that the first base station does not support slices or does not prefer to support slices, which improves information transmission efficiency.
  • FIG. 4 is a schematic flowchart of a method for receiving information according to an embodiment of the present disclosure.
  • the information receiving method shown in this embodiment may be applicable to a base station, the base station includes but is not limited to a 4G base station, a 5G base station, and a 6G base station, and the base station may be the first base station in the foregoing embodiment.
  • the first base station may communicate with a terminal serving as user equipment, and the second base station in the above embodiment, the terminal including but not limited to electronic devices such as mobile phones, tablet computers, wearable devices, sensors, and Internet of Things devices.
  • the terminal may be a terminal to which the information sending method described in any of the foregoing embodiments is applicable.
  • the information receiving method may include the following steps:
  • step S401 the slice information of the slice corresponding to the service initiated by the terminal and sent by the terminal is received.
  • the first base station may receive slice information of a slice sent by the terminal, and the slice corresponds to a service initiated by the terminal.
  • the slice information may include a slice identifier, for example, may be one or more of the following slice identifiers: single network slice selection assistance information S-NSSAI of the slice, slice/service type SST of the slice, The slice index slice index, or the access type defined by the operator corresponding to the slice.
  • the slice information may also be other information, as long as it is information that can uniquely indicate a slice, which is merely illustrative and not limiting.
  • the first base station may receive an AS message sent by the terminal, where the AS message carries the NAS message sent by the terminal to the core network, and the AS message carries slice information of the slice.
  • the NAS message may be information used by the terminal to request resources related to the service, for example, may be a message requesting to establish, modify, and activate a PDU session corresponding to the service.
  • step S402 it is determined according to the slice information whether to hand over the terminal to a second base station supporting the slice.
  • the first base station may determine whether to hand over the terminal to the second base station that supports slices according to the slice information.
  • the first base station may receive slice information sent by the terminal, and determine whether to switch the terminal to the second base station that supports the slice according to the slice information. Therefore, even if the first base station does not support the slice, the terminal can be handed over to the second base station to ensure that the terminal successfully establishes a PDU session, which improves processing efficiency.
  • the first base station may first determine whether the slice is supported, and in response to determining that the slice is not supported according to the slice information, switch the terminal to the second base station.
  • the first base station may further determine whether to support the slice preferentially.
  • the first base station switches the terminal to a second base station that preferentially supports the slice in response to determining that the slice is not preferentially supported according to the slice information.
  • the first base station may further determine whether to switch the terminal to the second base station that preferentially supports the slice according to its own situation. For example, the first base station can determine whether the signal strength of the terminal is greater than a preset threshold. If it is greater than the preset threshold, the terminal does not need to be handed over to the second base station, and if it is not greater than the preset threshold, the terminal is switched to the second base station. Alternatively, it can be determined whether the load of the first base station itself is greater than the preset threshold, if not, the terminal does not need to be switched to the second base station, and if it is greater than the preset threshold, the terminal is switched to the second base station. Of course, the first base station may also make judgments based on other conditions, for example, a combination of its own load and signal strength to determine, etc. This embodiment is only illustrative, and not limiting.
  • the first base station determines that the terminal needs to be handed over to the second base station, it also needs to process the received NAS message, where the NAS message is information corresponding to a slice, for example, it can be a request that matches the Messages of PDU session-related resources corresponding to the slice, such as a PDU session establishment request.
  • the NAS message is information corresponding to a slice, for example, it can be a request that matches the Messages of PDU session-related resources corresponding to the slice, such as a PDU session establishment request.
  • FIG. 5 takes FIG. 5 as an example for illustrative description.
  • FIG. 5 is a schematic flowchart of another method for receiving information according to an embodiment of the present disclosure. As shown in Figure 5, the method further includes:
  • step S501 a non-access stratum message sent by the terminal is received and buffered.
  • the first base station after receiving the NAS message sent by the terminal, the first base station does not directly send the NAS message to the core network, but first caches the NAS message locally.
  • the first base station may use different handover modes to switch the terminal to the second base station, and corresponding to different handover modes, the first base station may use different modes to process the received NAS message. If the NG handover method is adopted, the first base station may process the received NAS message according to step S502; or, if the Xn handover method is adopted, the first base station may process the received NAS message according to step S503.
  • step S502 in response to the terminal being handed over to the second base station through NG handover, the non-access stratum message is sent to the core network.
  • the first base station may switch the terminal to the second base station by adopting an NG handover manner.
  • the first base station may send a request to the core network to switch the terminal to the second base station through the NG interface, and after receiving the instruction to release the terminal context sent by the core network, the first base station sends the cached NAS message to the core network.
  • the first base station may encapsulate the NAS message into an NG message separately and send it to the core network, or the first base station may also carry the NAS message in the response information that the terminal context is successfully released.
  • the core network receives the NAS message, and the core network determines that the terminal has accessed the second base station, and thus, for the NAS message, the core network responds to the NAS message based on the second base station.
  • the core network may instruct the second base station to allocate resources for the PDU session.
  • step S503 in response to handover of the terminal to the second base station through Xn handover, the non-access stratum message is sent to the second base station.
  • the first base station may forward the NAS message to the core network through the second base station.
  • the first base station may send the NAS message to the second base station, and after receiving the second base station, the second base station may send the NAS message to the core network.
  • the first base station may switch the terminal to the second base station by means of Xn handover.
  • the first base station may send a request for handover of the terminal to the second base station to the second base station through the Xn interface, and in response to the second base station accepting the handover request, the first base station may send the buffered NAS message through the Xn interface message sent to the second base station.
  • the second base station can forward the NAS message to the core network.
  • the second base station may send the NAS message when sending the path switching request of the terminal to the core network, for example, carry the NAS message in the path switching request.
  • the second base station may first send a path switching request to the core network, and in response to the core network accepting the request, the second base station sends the NAS message to the core network separately.
  • the first base station can hand over the terminal to the second base station, and sends the NAS message to the core network after the handover is completed.
  • the core network can determine that the terminal has accessed the second base station, and respond to the request of the terminal through the second base station, avoiding the problem that the terminal request fails because the first base station does not support slicing.
  • the first base station may continue to forward the NAS message while triggering the terminal to switch to the second base station, that is, the first base station does not need to wait for the terminal handover to be completed, but continues to forward the NAS message.
  • FIG. 6 takes FIG. 6 as an example for illustrative description.
  • FIG. 6 is a schematic flowchart of another method for receiving information according to an embodiment of the present disclosure. As shown in Figure 6, the method further includes:
  • step S601 the non-access stratum message sent by the terminal is received, and the non-access stratum message is sent to the core network.
  • the first base station after receiving the NAS message sent by the terminal, directly sends the NAS message to the core network without buffering.
  • step S602 send first indication information to the core network, where the first indication information is used to instruct the core network to switch the terminal to the second base station at the first base station Before ending, stop responding to the non-access stratum message.
  • the core network may indicate that the terminal is currently A handover is made to instruct the core network to stop responding to the NAS message.
  • the first base station may send first indication information to the core network, where the first indication information may instruct the core network to, before the action of the first base station switching the terminal to the second base station ends, Stop responding to the NAS message.
  • the core network may respond to the NAS message after detecting that the action of switching the terminal to the second base station ends.
  • the core network may respond to the NAS message when detecting that the terminal succeeds, fails, or cancels the handover to the second base station.
  • the core network can detect the success or cancellation. If the terminal accesses the second base station successfully, the core network can respond to the NAS message through the second base station; if the terminal cancels accessing the second base station, the core network can still respond to the NAS message through the first base station.
  • the core network can determine by itself whether the terminal fails to switch to the second base station. For example, the core network can activate a timer after receiving the first indication information sent by the first base station. When the timer expires, if the core network does not detect that the terminal successfully accesses the second base station and does not detect that the terminal cancels access to the second base station, the core network can determine that the terminal has failed to switch to the second base station, and can still respond to the NAS message through the first base station.
  • the core network may also determine, according to the instruction of the first base station, whether the action of switching the terminal to the second base station ends.
  • FIG. 7 is a schematic flowchart of another method for receiving information according to an embodiment of the present disclosure. As shown in Figure 7, the method further includes:
  • step S701 in response to the end of the action of switching the terminal to the second base station, send second indication information to the core network, where the second indication information is used to indicate the core network Continue to respond to the non-access stratum message.
  • the first base station may send second indication information to the core network after the handover of the terminal to the second base station ends, for example, after the terminal fails to switch to the second base station, to instruct the core network to The handover action has ended, so that the core network can continue to respond to NAS messages.
  • the core network may respond to the NAS message through the first base station.
  • the first base station may use NG handover or Xn handover to switch the terminal to the second base station, and at the same time, the first base station may also indicate to the core network that the terminal is being handed over by using the first indication information, and The terminal is instructed to end the handover to the core network through the second indication information.
  • the first base station may switch the terminal to the second base station by adopting an NG handover manner.
  • the first base station sends the first indication information to the core network.
  • the first indication information may be an NG message sent by the first base station, and the NG message may carry indication information that the terminal is performing NG handover; or, the first indication information may also be in the existing handover process.
  • the Handover Required message the first base station sends the Handover Required message together with the NAS message to the core network. Therefore, after receiving the first indication information, the core network can determine that the terminal is performing handover, so it can stop responding to the NAS message, or the core network can also set and activate a timer after receiving the first indication information.
  • the core network may further receive the second indication information.
  • the second indication information may be sent by the first base station.
  • the first base station may send a handover cancellation request or a handover failure message to the core network; or, the second indication information It can also be sent by the second base station.
  • the second base station can send a Handover Notify message to the core network.
  • the core network may determine that the action of the first base station switching the terminal to the second base station is over, so that the core network continues to respond to the NAS message.
  • the core network may not determine whether the handover action ends according to the second indication information, but determine according to a timer activated after receiving the first indication information, for example, after the timer expires, the core network does not receive
  • the core network may determine that the terminal handover fails, so that the core network continues to respond to the NAS message.
  • the first base station may switch the terminal to the second base station by means of Xn handover.
  • the first base station sends the first indication information to the core network.
  • the first indication information may be an Xn message sent by the first base station, and the Xn message may carry indication information that the terminal is performing Xn handover. Therefore, after receiving the first indication information, the core network can determine that the terminal is performing handover, so it can stop responding to the NAS message, or the core network can also set and activate the timing after receiving the first indication information at the same time device.
  • the core network may further receive the second indication information sent by the first base station. For example, when the terminal cancels the handover or the handover fails, the first base station may send a handover cancellation request or a handover failure message to the core network; when the terminal is handed over successfully, the first base station may send a path switching request to the core network. After receiving the second indication information, the core network may determine that the action of the first base station switching the terminal to the second base station is over, so that the core network continues to respond to the NAS message.
  • the core network may also not determine whether the handover action ends according to the second indication information, but determine according to the timer activated when the first indication information is received and the response to the NAS message is stopped, for example, when the timer expires After the period, when the core network does not receive a handover failure message, a path switching request, or a handover cancellation request, the core network can determine that the terminal handover fails, so that the core network continues to respond to the NAS message.
  • the first base station directly sends the NAS message to the core network without waiting for the terminal to successfully switch to the second base station, and instructs the core network to stop and resume responding to the NAS message through the first indication information, the second indication information, etc. the response to. Therefore, on the basis of avoiding the failure of the terminal request due to the fact that the first base station does not support slicing, the processing efficiency of the NAS message by the first base station is also improved.
  • the present disclosure also provides embodiments of an information sending apparatus.
  • FIG. 8 is a schematic block diagram of an information sending apparatus according to an embodiment of the present disclosure.
  • the information sending apparatus shown in this embodiment may be applicable to terminals, and the terminals include but are not limited to electronic devices such as mobile phones, tablet computers, wearable devices, sensors, and Internet of Things devices.
  • the terminal may communicate with a base station as a user equipment, and the base station includes but is not limited to a 4G base station, a 5G base station, and a 6G base station.
  • the base station may be the first base station and/or the first base station in any subsequent embodiment. or the second base station.
  • the device includes:
  • the information determination module 801 is configured to determine the slice information of the slice corresponding to the initiated service
  • the slice information is used for the first base station to determine whether to hand over the terminal to the second base station that supports the slice
  • the slice information is used for the first base station to hand over the terminal to the second base station when it is determined that the first base station does not support the slice.
  • the slice information is used for the first base station to switch the terminal to a second base station that preferentially supports the slice in the case that it is determined that the first base station does not preferentially support the slice.
  • the information determination module 801 is specifically configured to:
  • the slice information of the slice corresponding to the service is determined by the non-access layer
  • the slice information is sent to the access stratum through the non-access stratum.
  • the information sending module 802 is specifically configured as:
  • the slice information is carried in the access stratum AS message used for sending the non-access stratum NAS message.
  • the information sending module 802 is specifically configured as:
  • the slice information is sent to the first base station in response to determining that the first base station does not support the slice or that the first base station does not preferentially support the slice.
  • the apparatus further includes:
  • the capability determination module 803 is configured to receive a system message SI or a radio resource control message RRC sent by the first base station, wherein the system message or the radio resource control message carries information about the support slice of the first base station and determining whether the first base station supports or preferentially supports the slice according to the capability information of the first base station about supporting slices.
  • the slice information is at least one of the following:
  • the present disclosure also provides an embodiment of an information receiving apparatus.
  • FIG. 9 is a schematic block diagram of an information receiving apparatus according to an embodiment of the present disclosure.
  • the information receiving apparatus shown in this embodiment may be applicable to a base station, the base station includes but is not limited to a 4G base station, a 5G base station, and a 6G base station, and the base station may be the first base station in the foregoing embodiment.
  • the first base station may communicate with a terminal serving as user equipment, and the second base station in the above embodiment, the terminal including but not limited to electronic devices such as mobile phones, tablet computers, wearable devices, sensors, and Internet of Things devices.
  • the terminal may be a terminal to which the information sending method described in any of the foregoing embodiments is applicable.
  • the information receiving apparatus may include:
  • the information receiving module 901 is configured to receive the slice information of the slice corresponding to the service initiated by the terminal and sent by the terminal;
  • the handover module 902 is configured to determine whether to handover the terminal to a second base station supporting the slice according to the slice information.
  • the switching module 902 is specifically configured to: in response to determining that the slice is not supported according to the slice information, switch the terminal to the second base station.
  • the switching module 902 is specifically configured to: in response to determining that the slice is not preferentially supported according to the slice information, switch the terminal to a second base station that preferentially supports the slice.
  • the apparatus further includes:
  • the caching module 903 is configured to: receive and cache the non-access stratum message sent by the terminal; in response to switching the terminal to the second base station through NG handover, send the non-access stratum message to the core network;
  • the cache module 903 can also be configured to:
  • the apparatus further includes:
  • the first indication module 904 is configured to receive the non-access stratum message sent by the terminal, and send the non-access stratum message to the core network; send first indication information to the core network, wherein the first indication information is The indication information is used to instruct the core network to stop responding to the non-access stratum message before the first base station switches the terminal to the second base station.
  • the apparatus further includes:
  • the second indication module 905 is configured to, in response to the end of the action of switching the terminal to the second base station, send second indication information to the core network, where the second indication information is used to indicate The core network continues to respond to the non-access stratum message.
  • the slice information is at least one of the following:
  • the UE In order to solve the deployment scenario where different cells support different slices or different slices have different preferred frequencies/cells under TA, the UE currently resides in a cell that does not support a certain slice, causing the PDU session resource request corresponding to the slice to fail, which in turn causes the UE to fail to request PDU session resources.
  • the PDU session establishment request is rejected this time, or the current camping frequency/cell is not preferred for slices, resulting in poor service quality and other problems.
  • the UE sends the PDU session establishment request it also indicates the slice information corresponding to the PDU session in the AS message. , which is used to assist the RAN to determine whether to support/prefer to support the slice, and if not, pre-handover the UE to the cell that supports the slice or the preferred frequency/cell of the slice based on the slice information.
  • the UE reports the slice information corresponding to the NAS message to the base station, and the base station receives and performs pre-handover based on the slice information.
  • the UE Based on 1, if the UE knows whether the current cell supports the slice corresponding to the NAS message, only when the current cell does not support the slice, the UE reports the slice information to the base station when sending the NAS message.
  • the UE Based on 1, if based on the existing standard, that is, the UE does not know whether the current cell supports the slice corresponding to the NAS message, the UE always needs to report the slice information to the base station when sending the NAS message.
  • the NAS message is a PDU session establishment request.
  • the pre-handover refers to handover of the UE to a cell that supports/preferably supports the slice.
  • the slice information is determined by the UE NAS layer and provided to the AS layer.
  • the UE NAS layer can determine the S-NSSAI corresponding to the service according to the URSP rule provided by the PCF or locally configured and provide it to the AS layer.
  • the slice information may be included in Ulinformationtransfer or other AS messages and sent to the base station.
  • the NAS layer of the UE after determining that a new PDU session needs to be created, provides the NAS message of the PDU Session establishment request together with the slice information to the AS layer, which is encapsulated by the AS layer in a Ulinformationtransfer message and sent to the base station.
  • the slice information supported by the cell may be provided by the SIB message or the RRCRelease message or the NAS layer.
  • the base station determines whether the current cell of the UE supports/preferably supports the slice, and triggers a handover if it does not support or does not prefer to support the slice.
  • the base station determines whether to perform the handover by itself.
  • the base station when triggering the handover, can continue to forward the NAS message to the AMF, and can also cache the NAS message.
  • the base station Based on 10, if the base station buffers the NAS message, the base station will send the NAS message to the AMF after the handover is completed.
  • the base station caches the PDU session establishment request, and in the Xn handover, when the source base station receives the handover request response from the target base station, it forwards it to the target base station through the Xn interface message, and the target base station sends the PDU session establishment request together with the path switching request to the AMF or It is sent to the AMF separately after receiving the path switch request response.
  • the base station caches the PDU session establishment request, and in the N2 handover, when the source base station receives the UE context release command from the AMF, it encapsulates it in an N2 message and sends it to the AMF, or it can be sent to the AMF together with the UE context release command completion message.
  • the base station Based on 10, if the base station continues to forward the NAS message while triggering the handover, the base station sends an indication to notify the AMF that the current base station is doing the handover. After receiving the indication, the AMF suspends the corresponding process of the NAS message unless it detects that the handover execution has been completed or the handover has been completed. If it fails/cancels, the process corresponding to the NAS message continues to be executed.
  • the base station can send a handover failure message to the AMF, or the AMF can configure and activate the timer locally after receiving the instruction from the base station. If the handover is not detected successfully or canceled before the timer expires, the handover is considered to be handed over. fail.
  • the base station can indicate the AMF in the N2 message forwarding the PDU session establishment request that the base station is doing Xn handover at this time.
  • the AMF After the AMF receives the instruction, it suspends the PDU session establishment process, and sets and activates the timer at the same time.
  • the AMF receives the source If the handover cancellation request (handover cancellation) or path switch request (handover success) or handover failure message sent by the base station or the local timer expires (handover failure), the PDU session establishment process is continued.
  • the base station can indicate that the base station is doing N2 handover in the N2 message containing the PDU session establishment request, or it can send the Handover Required message together with the PDU session establishment request to the AMF.
  • the AMF receives both Handover Required and PDU session establishment When requesting, suspend the PDU session establishment process, and set and activate the timer at the same time.
  • the AMF receives the Handover Notify message sent by the target base station (successful handover) or the handover cancellation request (handover cancellation) sent by the source base station, or the handover failure message or local timing If the device expires (handover failure), continue to execute the PDU session establishment process.
  • the slice information can be S-NSSAI, or SST, slice index, operator-defined access type, or any other information that can uniquely indicate slices.
  • Embodiments of the present disclosure also provide an electronic device, including:
  • memory for storing processor-executable instructions
  • the processor is configured to implement the above-mentioned information sending method and/or information receiving method.
  • Embodiments of the present disclosure also provide a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the steps in the above-mentioned information sending method and/or information receiving method.
  • FIG. 10 is a schematic block diagram of an apparatus 1000 for receiving information according to an embodiment of the present disclosure.
  • the apparatus 1000 may be provided as a base station.
  • apparatus 1000 includes a processing component 1022, a wireless transmit/receive component 1024, an antenna component 1026, and a signal processing portion specific to a wireless interface, and the processing component 1022 may further include one or more processors.
  • One of the processors in the processing component 1022 can be configured to implement the method of receiving information.
  • FIG. 11 is a schematic block diagram of an apparatus 1100 for sending information according to an embodiment of the present disclosure.
  • apparatus 1100 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, and the like.
  • the apparatus 1100 may include one or more of the following components: a processing component 1102, a memory 1104, a power supply component 1106, a multimedia component 1108, an audio component 1110, an input/output (I/O) interface 1112, a sensor component 1114, and communication component 1116.
  • a processing component 1102 a memory 1104, a power supply component 1106, a multimedia component 1108, an audio component 1110, an input/output (I/O) interface 1112, a sensor component 1114, and communication component 1116.
  • the processing component 1102 generally controls the overall operation of the device 1100, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 1102 may include one or more processors 1120 to execute instructions to complete all or part of the steps of the above-described information sending method.
  • processing component 1102 may include one or more modules that facilitate interaction between processing component 1102 and other components.
  • processing component 1102 may include a multimedia module to facilitate interaction between multimedia component 1108 and processing component 1102.
  • Memory 1104 is configured to store various types of data to support operations at device 1100 . Examples of such data include instructions for any application or method operating on the device 1100, contact data, phonebook data, messages, pictures, videos, and the like. Memory 1104 may be implemented by any type of volatile or non-volatile storage device or combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Magnetic or Optical Disk Magnetic Disk
  • Power component 1106 provides power to various components of device 1100 .
  • Power components 1106 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 1100 .
  • Multimedia component 1108 includes a screen that provides an output interface between the device 1100 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user.
  • the touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.
  • the multimedia component 1108 includes a front-facing camera and/or a rear-facing camera. When the device 1100 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each of the front and rear cameras can be a fixed optical lens system or have focal length and optical zoom capability.
  • Audio component 1110 is configured to output and/or input audio signals.
  • audio component 1110 includes a microphone (MIC) that is configured to receive external audio signals when device 1100 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signal may be further stored in memory 1104 or transmitted via communication component 1116 .
  • audio component 1110 also includes a speaker for outputting audio signals.
  • the I/O interface 1112 provides an interface between the processing component 1102 and a peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to: home button, volume buttons, start button, and lock button.
  • Sensor assembly 1114 includes one or more sensors for providing status assessment of various aspects of device 1100 .
  • the sensor assembly 1114 can detect the open/closed state of the device 1100, the relative positioning of components, such as the display and keypad of the device 1100, and the sensor assembly 1114 can also detect a change in the position of the device 1100 or a component of the device 1100 , the presence or absence of user contact with the device 1100 , the device 1100 orientation or acceleration/deceleration and the temperature change of the device 1100 .
  • Sensor assembly 1114 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact.
  • Sensor assembly 1114 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 1114 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 1116 is configured to facilitate wired or wireless communication between apparatus 1100 and other devices.
  • the device 1100 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G LTE, 5G NR, or a combination thereof.
  • the communication component 1116 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 1116 also includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module may be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • apparatus 1100 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), a controller, a microcontroller, a microprocessor or other electronic components are implemented for implementing the above-mentioned information sending method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller a controller
  • microcontroller a microcontroller
  • microprocessor or other electronic components are implemented for implementing the above-mentioned information sending method.
  • a non-transitory computer-readable storage medium including instructions such as a memory 1104 including instructions, is also provided, and the instructions can be executed by the processor 1120 of the apparatus 1100 to complete the information sending method described above.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开涉及信息发送方法和装置、信息接收方法和装置，其中，所述信息发送方法包括：确定发起的业务对应切片的切片信息；向第一基站发送所述切片信息；其中，所述切片信息用于供第一基站确定是否将所述终端切换到支持所述切片的第二基站。根据本公开，终端向当前接入的第一基站发送切片的切片信息，则第一基站可以根据该切片信息确定是否将该终端切换到支持该切片的第二基站。从而，即使第一基站不支持该切片，也可以将终端切换到第二基站，以保证终端建立PDU会话成功，以及时基于该PDU会话进行通信。

Description

信息发送方法和装置、信息接收方法和装置 技术领域
本公开涉及通信技术领域，具体而言，涉及一种信息发送方法和装置、信息接收方法和装置，电子设备和计算机可读存储介质。
背景技术
网络切片，就是将一个物理网络划分成多个虚拟的逻辑网络，灵活地为不同用户提供差异化服务。一般的，为了对每个网络切片进行管理，每个网络切片具有唯一对应的切片标识，且不同切片的流量可以由不同的协议数据单元PDU(Protocol Data Unit)会话进行处理。
在相关技术中，当有业务需要启动时，终端为该业务确定对应的PDU会话，并确定该PDU会话对应的切片信息。然后，终端向核心网发送非接入层NAS(Non-access stratum)信息，并该NAS消息中携带对应的切片信息，请求获取该PDU会话的相关资源。从而，核心网可以指示接入网RAN为该PDU会话分配相应的资源。
然而，若RAN不支持上述PDU会话所对应的切片，RAN可以拒绝为该PDU会话分配资源，从而导致终端的请求失败。
发明内容
有鉴于此，本公开的实施例提出了一种信息发送方法和装置、信息接收方法和装置，以解决相关技术中的技术问题。
根据本公开实施例的第一方面，提出一种信息发送方法，应用于终端，所述方法包括：
确定发起的业务对应切片的切片信息；
向第一基站发送所述切片信息；
其中，所述切片信息用于供第一基站确定是否将所述终端切换到支持所述切片的第二基站。
根据本公开实施例的第二方面，提出一种信息发送装置，应用于终端，所述装 置包括：
信息确定模块，被配置为确定发起的业务对应切片的切片信息；
信息发送模块，被配置为向第一基站发送所述切片信息；
其中，所述切片信息用于供第一基站确定是否将所述终端切换到支持所述切片的第二基站。
根据本公开实施例的第三方面，提出一种信息接收方法，应用于第一基站，所述方法包括：
接收终端发送的与所述终端发起的业务对应切片的切片信息；
根据所述切片信息确定是否将所述终端切换到支持所述切片的第二基站。
根据本公开实施例的第四方面，提出一种接收装置，应用于第一基站，所述装置包括：
信息接收模块，被配置为接收终端发送的与所述终端发起的业务对应切片的切片信息；
切换模块，被配置为根据所述切片信息确定是否将所述终端切换到支持所述切片的第二基站。
根据本公开实施例的第五方面，提出一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为实现上述第一方面和/或第二方面的方法。
根据本公开实施例的第六方面，提出一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现第一方面和/或第二方面的方法中的步骤。
根据本公开的实施例，终端向当前接入的第一基站发送切片的切片信息，则第一基站可以根据该切片信息确定是否将该终端切换到支持或首选支持该切片的第二基站。从而，即使第一基站不支持该切片，也可以将终端切换到第二基站，以保证终端建立PDU会话成功，以及时基于该PDU会话进行通信。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是根据本公开的实施例示出的一种信息发送方法的示意流程图。
图2是根据本公开的实施例示出的另一种信息发送方法的示意流程图。
图3是根据本公开的实施例示出的另一种信息发送方法的示意流程图。
图4是根据本公开的实施例示出的一种信息接收方法的示意流程图。
图5是根据本公开的实施例示出的另一种信息接收方法的示意流程图。
图6是根据本公开的实施例示出的另一种信息接收方法的示意流程图。
图7是根据本公开的实施例示出的另一种信息接收方法的示意流程图。
图8是根据本公开的实施例示出的一种信息发送装置的示意框图。
图9是根据本公开的实施例示出的一种信息接收装置的示意框图。
图10是根据本公开的实施例示出的一种用于信息接收的装置的示意框图。
图11是根据本公开的实施例示出的一种用于信息发送的装置的示意框图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
在相关技术中，终端中可以预设有业务与网络切片的对应关系，例如，终端可以通过URSP(UE Route Selection Policy，UE路由选择策略)来记录业务与网络切片的对应关系。在URSP中，可以包括一个或多个URSP规则，且每个URSP规则可以包括规则优先级、业务描述符Traffic Descriptor和RSD(Route selection descriptor，路径选择描述符)列表list等，其中，RSD list中可以包括网络切片标识，例如一个或多 个单一网络切片选择辅助信息S-NSSAI。
当终端有业务需要启动时，终端可以确定该业务的Traffic Descriptor，然后在预设的URSP中查找是否相匹配的切片标识。针对该查找到的切片标识，若该切片标识存在对应的现有PDU会话，则将业务与该现有PDU会话关联；若该切片标识不存在对应的现有PDU会话，则建立新的PDU会话。
在一个实施例中，终端可以向网络发送NAS消息，以请求建立PDU会话、修改PDU会话、或激活PDU会话。终端可以通过当前服务基站向核心网发送NAS消息，并在该NAS消息中携带与PDU会话对应的切片信息。若核心网接受该PDU会话的建立、修改或激活，则核心网可以指示基站为该PDU会话分配资源。
在一个实施例中，若终端处于多个小区重叠覆盖的位置，则终端在切片注册时，核心网会将覆盖该终端的所有基站所支持的切片，均设置为允许该终端使用的切片，例如可以将覆盖终端的所有小区所支持的切片标识S-NSSAI的集合，设置为允许该终端使用的切片标识Allowed NSSAI。
在一个实施例中，不同基站所支持的切片可以是不同的。以基站1支持切片1，基站2支持切片2为例，该切片1和切片2均为允许终端使用的切片。
在终端处于基站1和基站2重叠覆盖的位置，且基站1为终端的服务基站终端在发起业务时，若需要使用切片2对应的PDU会话，终端通过当前接入的基站1向核心网发送NAS消息请求为该PDU会话分配资源，核心网在接受该NAS消息后，可以指示基站1为终端分配相关资源。然而，基站1支持切片1，而并不支持切片2，那么基站1会拒绝为该PDU会话分配资源。由此，导致终端为该PDU会话分配资源的请求失败。
在一个实施例中，不同基站所支持的切片也可以是相同的，但不同基站首选支持的切片是不同的。对于首选支持的切片，基站可以提供性能更好的服务；对于非首选支持的切片，可能会存在信号质量较差等问题。由此，若基站在非首选支持切片的基站建立该切片的通信，可能存在通信质量差的问题，用户体验不佳。
有鉴于此，本公开的实施例提出了一种信息发送、接收方法，本实施例方法中，终端向当前接入的第一基站发送切片的切片信息，则第一基站可以根据该切片信息确定是否将该终端切换到支持或首选支持该切片的第二基站。从而，即使第一基站不支持该切片，也可以将终端切换到第二基站，以保证终端建立PDU会话成功，提高了处 理效率。
图1是根据本公开的实施例示出的一种信息发送方法的示意流程图。本实施例所示的信息发送方法可以适用于终端，所述终端包括但不限于手机、平板电脑、可穿戴设备、传感器、物联网设备等电子设备。所述终端可以作为用户设备与基站通信，所述基站包括但不限于4G基站、5G基站、6G基站，在一个实施例中，所述基站可以是后续任一实施例中的第一基站和/或第二基站。
如图1所示，所述信息发送方法可以包括以下步骤：
在步骤S101中，确定发起的业务对应切片的切片信息。
在一个实施例中，终端可以为将要发起的业务确定对应的PDU会话，例如可以是建立、修改或激活PDU会话，并确定该PDU会话对应切片的切片信息。
在一个实施例中，该切片信息可以包括切片标识，例如可以是以下切片标识的中的一个或多个：切片的单一网络切片选择辅助信息S-NSSAI，切片的切片/服务类型SST，切片的切片索引slice index，或者切片对应的运营商定义的接入类型。或者，切片信息还可以是其他信息，只要是可以唯一指示切片的信息即可，这里只是示例性说明，并不进行限定。
在步骤S102中，向第一基站发送所述切片信息。
其中，所述切片信息用于供第一基站确定是否将所述终端切换到支持所述切片的第二基站。
根据本公开的实施例，终端向当前接入的第一基站发送切片的切片信息，使得第一基站可以根据该切片信息确定是否将该终端切换到支持该切片的第二基站。从而即使第一基站不支持该切片，也可以将终端切换到第二基站，以保证终端建立PDU会话成功，以及时基于该PDU会话进行通信。
需要说明的是，终端通过第一基站向核心网发送的NAS消息中可以包含切片信息，但由于第一基站不会对NAS消息进行解析，因此，终端还需要在发送给第一基站的AS消息中携带切片信息。
在一个实施例中，终端可以在用于发送NAS消息的AS消息中，携带所述切片信息。
在一个实施例中，该AS消息可以ULinformationtransfer消息，终端可以在 ULinformationtransfer消息中携带该切片信息。
举例来说，该非接入层NAS消息可以是请求核心网分配PDU会话相关资源的消息，例如可以是PDU会话的建立、修改或激活请求。终端可以向第一基站发送该NAS消息，并在承载该NAS消息的AS消息(例如ULinformationtransfer消息)中也包含该切片信息。从而，终端向第一基站发送一条信息，既可以通过第一基站向核心网转发该NAS消息，又可以通过该AS消息使第一基站获知该NAS消息对应的切片信息，信息传输效率高，节省通信资源。
在一个实施例中，第一基站在接收到该切片的切片信息后，可以确定是否将所述终端切换到支持所述切片的第二基站。
在一个实施例中，第一基站在接收到该携带有切片信息的AS消息后，可以对该AS消息进行解析和后续处理。例如，第一基站可以从AS消息中解析获取切片信息，从而根据所述切片信息确定是否将所述终端切换到支持所述切片的第二基站。
在一个实施例中，切片信息用于供所述第一基站在确定所述第一基站不支持所述切片的情况下，将所述终端切换到所述第二基站。基于此，在一个实施例中，第一基站响应于根据所述切片信息确定不支持所述切片，将所述终端切换到所述第二基站。
在一个实施例中，切片信息用于供第一基站在确定所述第一基站不是首选支持所述切片的情况下，将所述终端切换至首选支持所述切片的第二基站。基于此，在一个实施例中，响应于根据所述切片信息确定不是首选支持所述切片，将所述终端切换到首选支持所述切片的第二基站。
在一个实施例中，终端在确定发起的业务后，由NAS层确定该业务对应的切片信息，而终端需要通过AS层将该切片信息发送给第一基站。在一个实施例中，终端可以采用图2的方法来确定切片信息。
图2是根据本公开的实施例示出的另一种信息发送方法的示意流程图。如图2所示，所述确定发起的业务对应切片的切片信息包括：
在步骤S201中，响应于所述业务要发起，通过非接入层确定所述业务对应切片的切片信息。
在一个实施例中，终端在确定要发起业务时，可以由终端中的NAS层对URSP规则进行匹配等方式，确定业务对应切片的切片信息。
在步骤S202中，通过非接入层将所述切片信息发送至接入层。
在一个实施例中，为了将该切片信息发送给第一基站，终端中的AS层可以从NAS层获取该切片信息。从而，可以将该切片信息携带在AS消息中，并将该AS消息发送给第一基站。
在一个实施例中，在终端中，NAS层可以先确定待发起业务对应切片的切片信息，再生成包括该切片信息的NAS消息，然后，AS层可以获取到该NAS消息，并获取该NAS消息中的切片信息。由此，AS层可以在AS消息中携带该切片信息，并通过该携带有切片信息的AS消息来发送NAS消息。
在一个实施例中，终端可以具有或者不具有获取第一基站关于支持切片的能力信息。
在一个实施例中，该第一基站关于支持切片的能力信息可以包括第一基站是否支持切片。或者，该第一基站关于支持切片的能力信息可以包括第一基站首选支持的切片，例如可以是所支持的多个切片的优先级，从而终端可以根据优先级来确定第一基站首选支持的切片。
若终端不具有获取第一基站关于支持切片的能力信息，即终端无法确定第一基站是否支持切片，或无法确定第一基站是否首选支持切片，则终端在向第一基站发送NAS消息时，还需要发送切片的切片信息。
若终端具有获取第一基站关于支持切片的能力信息，则终端可以先确定第一基站是否支持或是否首选支持所述切片。在一个实施例中，终端响应于确定所述第一基站不支持或确定所述第一基站不是首选支持所述切片，向所述第一基站发送所述切片信息。终端响应于第一基站支持或确定所述第一基站首选支持所述切片，无需向所述第一基站发送所述切片信息。
举例来说，终端在发起业务时，首先确定该业务对应的切片，然后确定第一基站是否支持该切片或是否首选支持该切片。若确定第一基站不支持该切片或不首选支持该切片，则终端在通过第一基站向核心网发送用于请求该业务相关资源的NAS消息时，还向第一基站发送切片信息。例如，终端可以在用于发送该NAS消息的AS消息中携带切片信息。由此，终端仅发送一条消息，既可以通过第一基站向核心网转发该NAS消息，又可以通过该AS消息使第一基站获知该NAS消息对应的切片，通信效率较高。
根据上述实施例，终端若具有获取第一基站关于支持切片的能力信息，则不需要在所有发送的NAS消息时均向第一基站发送切片信息，而是在确定第一基站不支持或不是首选支持切片时发送切片信息。由此，终端可以避免发送无用信息，提高信息传输效率。
在一个实施例，终端可以通过多种方式来获取第一基站支关于支持切片的能力信息。下面以图3为例进行示例性说明。
图3是根据本公开的实施例示出的另一种信息发送方法的示意流程图。如图3所示，所述方法还包括：
在步骤S301中，接收所述第一基站发送的系统消息SI或者无线资源控制消息RRC，其中，所述系统消息或者所述无线资源控制消息，携带有所述第一基站关于支持切片的能力信息。
在一个实施例中，关于支持切片的能力信息，可以包括第一基站所支持的各切片，或者也可以包括第一基站所首选支持的切片，或者也可以包括第一基站所支持各切片以及各切片的优先级等。
在一个实施例中，第一基站可以在发送的系统消息SI中携带第一基站关于支持切片的能力信息。例如，第一基站可以在广播发送的系统消息块SIB中携带该关于支持切片的能力信息。
在一个实施例中，第一基站可以在发送给终端的RRC消息中携带第一基站关于支持切片的能力信息。例如，第一基站可以在与终端建立连接后，通过RRC消息发送该关于支持切片的能力信息。
在一个实施例中，终端也可以不是从第一基站获取该第一基站关于支持切片的能力信息。例如，终端在接入第一基站之前，可以从接入的原基站获取到第一基站关于支持切片的能力信息，例如可以从原基站的RRC Release消息中获取。例如，终端还可以通过NAS层从核心网处获取第一基站关于支持切片的能力信息，例如核心网在为终端配置Allowed NSSAI时，还可以指示每个切片所对应的基站，比如针对每个切片，可以指示支持该切片的基站、或者首选支持该切片的基站等等。
需要说明的是，上述获取第一基站关于支持切片的能力信息的方法为示例性说明，在实际应用中终端还可以通过其他方法来获取，这里只是示例性说明，并不进行限定。
在步骤S302中，根据所述第一基站关于支持切片的能力信息确定所述第一基站是否支持或是否首选支持所述切片。
在一个实施例中，终端在获取到第一基站关于支持切片的能力信息后，若该能力信息中仅包括第一基站所支持的切片，则终端可以确定第一基站是否支持所述切片；若能力信息中包括第一基站所首选支持的切片，则终端可以确定第一基站是否首选支持所述切片。
根据图3所示的实施例，终端可以通过多种方式来获取第一基站关于支持切片的能力信息，从而根据该能力信息确定第一基站是否支持所述切片。因此，终端不需要在发送的NAS消息时始终均向第一基站发送切片信息，而是在确定第一基站不支持或不是首选支持切片时发送切片信息，提高了信息传输效率。
图4是根据本公开的实施例示出的一种信息接收方法的示意流程图。本实施例所示的信息接收方法可以适用于基站，所述基站包括但不限于4G基站、5G基站、6G基站，所述基站可以是上述实施例中的第一基站。所述第一基站可以与作为用户设备的终端、以及上述实施例中的第二基站进行通信，所述终端包括但不限于手机、平板电脑、可穿戴设备、传感器、物联网设备等电子设备。在一个实施例中，所述终端可以是上述任一实施例所述信息发送方法所适用的终端。
如图4所示，所述信息接收方法可以包括以下步骤：
在步骤S401中，接收终端发送的与所述终端发起的业务对应切片的切片信息。
在一个实施例中，第一基站可以接收终端发送的切片的切片信息，且该切片与终端发起的业务对应。
在一个实施例中，该切片信息可以包括切片标识，例如可以是以下切片标识的中的一个或多个：切片的单一网络切片选择辅助信息S-NSSAI，切片的切片/服务类型SST，切片的切片索引slice index，或者切片对应的运营商定义的接入类型。或者，切片信息还可以是其他信息，只要是可以唯一指示切片的信息即可，这里只是示例性说明，并不进行限定。
在一个实施例中，第一基站可以接收终端发送的AS消息，该AS消息中承载有终端发送至核心网的NAS消息，并且，该AS消息中携带有切片的切片信息。
在一个实施例中，该NAS消息可以是终端用于请求与业务相关资源的信息，例如，可以是请求建立、修改、激活与业务对应的PDU会话的消息。
在步骤S402中，根据所述切片信息确定是否将所述终端切换到支持所述切片的第二基站。
在一个实施例中，第一基站在接收到切片信息后，可以根据该切片信息确定是否将终端切换到支持接片的第二基站。
根据本公开的实施例，第一基站可以接收终端发送的切片信息，并根据该切片信息确定是否将该终端切换到支持该切片的第二基站。从而，即使第一基站不支持该切片，也可以将终端切换到第二基站，以保证终端建立PDU会话成功，提高了处理效率。
在一个实施例中，第一基站可以先判断是否支持该切片，响应于根据所述切片信息确定不支持所述切片，将所述终端切换到所述第二基站。
在一个实施例中，第一基站在确定可以支持该切片的基础上，还可以确定是否首选支持该切片。
在一个实施例中，第一基站响应于根据所述切片信息确定不是首选支持所述切片，将所述终端切换到首选支持所述切片的第二基站。
在一个实施例中，第一基站响应于根据所述切片信息确定不是首选支持所述切片，还可以根据自身的情况确定是否将终端切换到首选支持所述切片的第二基站。举例来说，第一基站可以确定终端的信号强度是否大于预设阈值，若大于预设阈值，则无需将终端切换到第二基站，若不大于预设阈值，则将终端切换到第二基站；或者可以确定第一基站自身的负载是否大于预设阈值，若不大于预设阈值，则无需将终端切换到第二基站，若大于预设阈值，则将终端切换到第二基站。当然，第一基站还可以基于其他条件进行判断，例如将自身负载和信号强度综合起来确定等，本实施例只是示例性说明，并不进行限定。
在一个实施例中，第一基站在确定需要将终端切换到第二基站后，同时还需要对接收到的NAS消息进行处理，其中，NAS消息为与切片对应的信息，例如可以是请求与该切片相对应的PDU会话相关资源的消息，比如PDU会话建立请求等。下面以图5为例进行示例性说明。
图5是根据本公开的实施例示出的另一种信息接收方法的示意流程图。如图5所示，所述方法还包括：
在步骤S501中，接收并缓存所述终端发送的非接入层消息。
在一个实施例中，第一基站在接收到终端发送的NAS消息后，不是直接将该NAS消息发送给核心网，而是先将NAS消息缓存到本地。
在一个实施例中，第一基站可以采用不同的切换方式将终端切换到第二基站，对应于不同的切换方式，第一基站可以采用不同的方式来处理接收到的NAS消息。若采用NG切换的方式，第一基站可以根据步骤S502来处理接收到的NAS消息；或者，若采用Xn切换的方式，第一基站可以根据步骤S503来处理接收到的NAS消息。
在步骤S502中，响应于通过NG切换将所述终端切换到所述第二基站，将所述非接入层消息发送至核心网。
在一个实施例中，第一基站可以采用NG切换的方式，将终端切换到第二基站。
在一个实施例中，第一基站可以通过NG接口向核心网发送将终端切换到第二基站的请求，在接收到核心网发送的释放终端上下文的指示后，第一基站将缓存的NAS消息发送给核心网。例如，第一基站可以将该NAS消息单独封装到NG消息中发送给核心网，或者第一基站也可以将该NAS消息携带在释放终端上下文成功的响应信息中。
在一个实施例中，核心网接收到该NAS消息，并且核心网确定终端已经接入到第二基站，由此，针对该NAS消息，核心网基于第二基站对该NAS消息进行响应。
举例来说，若该NAS消息为PDU会话的建立请求，核心网可以指示第二基站为该PDU会话分配资源。
在步骤S503中，响应于通过Xn切换将所述终端切换到所述第二基站，将所述非接入层消息发送至第二基站。
在一个实施例中，第一基站可以通过所述第二基站将所述NAS消息转发至核心网。第一基站可以将NAS消息发送给第二基站，第二基站接收到后，可以将该NAS消息发送给核心网。
在一个实施例中，第一基站可以采用Xn切换的方式，将终端切换到第二基站。
在一个实施例中，第一基站可以通过Xn接口向第二基站发送终端切换到第二基站的请求，响应于第二基站接受该切换请求，第一基站可以通过Xn接口消息将缓存的NAS消息发送给第二基站。由此，第二基站可以将该NAS消息转发给核心网。
在一个实施例中，第二基站可以在向核心网发送该终端的路径切换请求的同时 发送该NAS消息，例如将NAS消息携带在该路径切换请求中。或者，第二基站可以先向核心网发送路径切换请求，响应于核心网接受该请求，第二基站再单独将NAS消息发送给核心网。
根据上述实施例，第一基站可以将终端切换到第二基站，并且在切换完成后再将NAS消息发送给核心网。由此，核心网可以确定终端已接入第二基站，并通过第二基站响应终端的请求，避免因第一基站不支持切片而导致终端请求失败的问题。
在一个实施例中，第一基站可以触发终端切换到第二基站的同时，继续转发该NAS消息，也就是说，第一基站无需等待终端切换完成，而是继续转发NAS消息。下面以图6为例进行示例性说明。
图6是根据本公开的实施例示出的另一种信息接收方法的示意流程图。如图6所示，所述方法还包括：
在步骤S601中，接收终端发送的非接入层消息，并将所述非接入层消息发送至核心网。
在一个实施例中，第一基站在接收到终端发送的NAS消息后，无需进行缓存，而是直接将该NAS消息发送至核心网。
在步骤S602中，向所述核心网发送第一指示信息，其中，所述第一指示信息用于指示所述核心网在所述第一基站将所述终端切换到所述第二基站的动作结束之前，停止响应所述非接入层消息。
在一个实施例中，第一基站若确定需要将终端切换到第二基站，为了避免核心网在接收到NAS消息后通过第一基站响应该NAS消息导致终端请求失败，可以指示核心网当前终端正在进行切换，从而指示核心网停止响应该NAS消息。
在一个实施例中，第一基站可以向核心网发送第一指示信息，该第一指示信息可以指示核心网在所述第一基站将所述终端切换到所述第二基站的动作结束之前，停止响应所述NAS消息。
在一个实施例中，核心网可以在检测终端切换到所述第二基站的动作结束后，再响应NAS消息。例如，核心网在检测到终端切换到第二基站成功、失败、或取消切换时，可以响应NAS消息。
在一个实施例中，若终端接入第二基站成功，或终端取消接入第二基站，则核 心网可以检测到成功或取消。若终端接入第二基站成功，则核心网可以通过第二基站响应NAS消息；若终端取消接入第二基站，则核心网仍可以通过第一基站响应NAS消息。
在一个实施例中，核心网可以自行判断终端切换到第二基站是否失败，例如，核心网可以在接收到第一基站发送的第一指示信息后激活定时器，在定时器到期时，若核心网未检测到终端成功接入第二基站且未检测到终端取消接入第二基站，则核心网可以确定终端切换到第二基站失败，从而仍可以通过第一基站响应NAS消息。
在一个实施例中，核心网也可以根据第一基站的指示，来确定终端切换到所述第二基站的动作是否结束。下面以图7为例进行示例性说明。
图7是根据本公开的实施例示出的另一种信息接收方法的示意流程图。如图7所示，所述方法还包括：
在步骤S701中，响应于所述将所述终端切换到所述第二基站的动作结束，向所述核心网发送第二指示信息，其中，所述第二指示信息用于指示所述核心网继续响应所述非接入层消息。
在一个实施例中，第一基站在所述终端切换到所述第二基站的动作结束后，例如终端切换到第二基站失败后，可以向核心网发送第二指示信息，以指示核心网该切换动作已结束，从而核心网可以继续响应NAS消息。
在一个实施例中，若终端切换到第二基站失败，核心网可以通过第一基站响应NAS消息。
在一个实施例中，第一基站可以采用NG切换或Xn切换的方式，将终端切换到第二基站，同时，第一基站还可以通过第一指示信息来向核心网指示终端正在进行切换，以及通过第二指示信息来向核心网指示终端结束切换。下面结合具体的实施例对上述图6、图7所示的方法进行说明。
在一个实施例中，第一基站可以采用NG切换的方式，将终端切换到第二基站。
在一个实施例中，第一基站向核心网发送第一指示信息。举例来说，该第一指示信息可以是第一基站发送的一个NG消息，该NG消息可以携带有终端正在执行NG切换的指示信息；或者，该第一指示信息也可以是现有切换流程中的Handover Required消息，第一基站将该Handover Required消息与NAS消息一起发送给核心网。从而，核心网在接收到该第一指示信息后，可以确定终端正在执行切换，因此可以停止对NAS 消息的响应，或者核心网还可以在接收到第一指示信息之后同时设置并激活定时器。
在一个实施例中，在终端结束切换后，核心网还可以接收到第二指示信息。举例来说，该第二指示信息可以是第一基站发送的，例如当终端取消切换或切换失败时，第一基站可以向核心网发送切换取消请求或切换失败消息；或者，该第二指示信息也可以是第二基站发送的，例如当终端切换成功时，第二基站可以向核心网发送Handover Notify消息。核心网在接收到该第二指示信息后，可以确定第一基站将终端切换到第二基站的动作结束，从而核心网继续对NAS消息进行响应。
或者，核心网也可以不根据第二指示信息来确定切换动作是否结束，而是根据在接收到第一指示信息之后所激活的定时器来确定，例如在定时器到期后，核心网未接收到切换成功消息或切换取消请求时，核心网可以确定终端切换失败，从而核心网继续对NAS消息进行响应。
在一个实施例中，第一基站可以采用Xn切换的方式，将终端切换到第二基站。
在一个实施例中，第一基站向核心网发送第一指示信息。举例来说，该第一指示信息可以是第一基站发送的一个Xn消息，该Xn消息可以携带有终端正在执行Xn切换的指示信息。从而，核心网在接收到该第一指示信息后，可以确定终端正在执行切换，因此可以停止对NAS消息的响应，或者核心网还可以还可以在接收到第一指示信息之后同时设置并激活定时器。
在一个实施例中，在终端结束切换后，核心网还可以接收到第一基站发送的第二指示信息。举例来说，当终端取消切换或切换失败时，第一基站可以向核心网发送切换取消请求或切换失败消息；当终端切换成功时，第一基站可以向核心网发送路径切换请求。核心网在接收到该第二指示信息后，可以确定第一基站将终端切换到第二基站的动作结束，从而核心网继续对NAS消息进行响应。
或者，核心网也可以不根据第二指示信息来确定切换动作是否结束，而是根据在接收到第一指示信息在停止对NAS消息的响应时所激活的定时器来确定，例如在定时器到期后，核心网未接收到切换失败消息、路径切换请求、切换取消请求时，核心网可以确定终端切换失败，从而核心网继续对NAS消息进行响应。
根据上述实施例，第一基站无需等待终端成功切换到第二基站，就直接将NAS消息发送给核心网，并通过第一指示信息、第二指示信息等，指示核心网停止和恢复对NAS消息的响应。由此，在避免因第一基站不支持切片而导致终端请求失败的基础 上，还提高了第一基站对NAS消息的处理效率。
与前述的方法的实施例相对应，本公开还提供了信息发送装置的实施例。
图8是根据本公开的实施例示出的一种信息发送装置的示意框图。本实施例所示的信息发送装置可以适用于终端，所述终端包括但不限于手机、平板电脑、可穿戴设备、传感器、物联网设备等电子设备。所述终端可以作为用户设备与基站通信，所述基站包括但不限于4G基站、5G基站、6G基站，在一个实施例中，所述基站可以是后续任一实施例中的第一基站和/或第二基站。
如图8所示，所述装置包括：
信息确定模块801，被配置为确定发起的业务对应切片的切片信息；
信息发送模块802，被配置为向第一基站发送所述切片信息；
其中，所述切片信息用于供第一基站确定是否将所述终端切换到支持所述切片的第二基站
在一个实施例中，所述切片信息用于供所述第一基站在确定所述第一基站不支持所述切片的情况下，将所述终端切换到所述第二基站。
在一个实施例中，所述切片信息用于供第一基站在确定所述第一基站不是首选支持所述切片的情况下，将所述终端切换至首选支持所述切片的第二基站。
在一个实施例中，所述信息确定模块801，具体被配置为：
响应于所述业务要发起，通过非接入层确定所述业务对应切片的切片信息；
通过非接入层将所述切片信息发送至接入层。
在一个实施例中，所述信息发送模块802，具体被配置为：
在用于发送非接入层NAS消息的接入层AS消息中，携带所述切片信息。
在一个实施例中，所述信息发送模块802，具体被配置为：
响应于确定所述第一基站不支持或确定所述第一基站不是首选支持所述切片，向所述第一基站发送所述切片信息。
在一个实施例中，所述装置还包括：
能力确定模块803，被配置为接收所述第一基站发送的系统消息SI或者无线资源控制消息RRC，其中，所述系统消息或者所述无线资源控制消息，携带有所述第一 基站关于支持切片的能力信息；根据所述第一基站关于支持切片的能力信息确定所述第一基站是否支持或是否首选支持所述切片。
在一个实施例中，所述切片信息为以下至少一个：
切片的S-NSSAI；
切片的SST；
切片的slice index；
切片对应的运营商定义的接入类型。
与前述的信息接收方法的实施例相对应，本公开还提供了信息接收装置的实施例。
图9是根据本公开的实施例示出的一种信息接收装置的示意框图。本实施例所示的信息接收装置可以适用于基站，所述基站包括但不限于4G基站、5G基站、6G基站，所述基站可以是上述实施例中的第一基站。所述第一基站可以与作为用户设备的终端、以及上述实施例中的第二基站进行通信，所述终端包括但不限于手机、平板电脑、可穿戴设备、传感器、物联网设备等电子设备。在一个实施例中，所述终端可以是上述任一实施例所述信息发送方法所适用的终端。
如图9所示，所述信息接收装置可以包括：
信息接收模块901，被配置为接收终端发送的与所述终端发起的业务对应切片的切片信息；
切换模块902，被配置为根据所述切片信息确定是否将所述终端切换到支持所述切片的第二基站。
在一个实施例中，所述切换模块902，具体被配置为：响应于根据所述切片信息确定不支持所述切片，将所述终端切换到所述第二基站。
在一个实施例中，所述切换模块902，具体被配置为：响应于根据所述切片信息确定不是首选支持所述切片，将所述终端切换到首选支持所述切片的第二基站。
在一个实施例中，所述装置还包括：
缓存模块903，被配置为：接收并缓存所述终端发送的非接入层消息；响应于通过NG切换将所述终端切换到所述第二基站，将所述非接入层消息发送至核心网；
在一个实施例中，所述缓存模块903，还可以被配置为：
接收并缓存所述终端发送的非接入层消息；响应于通过Xn切换将所述终端切换到所述第二基站，将所述非接入层消息发送至第二基站。
在一个实施例中，所述装置还包括：
第一指示模块904，被配置为接收终端发送的非接入层消息，并将所述非接入层消息发送至核心网；向所述核心网发送第一指示信息，其中，所述第一指示信息用于指示所述核心网在所述第一基站将所述终端切换到所述第二基站的动作结束之前，停止响应所述非接入层消息。
在一个实施例中，所述装置还包括：
第二指示模块905，被配置为响应于所述将所述终端切换到所述第二基站的动作结束，向所述核心网发送第二指示信息，其中，所述第二指示信息用于指示所述核心网继续响应所述非接入层消息。
在一个实施例中，所述切片信息为以下至少一个：
切片的S-NSSAI；
切片的SST；
切片的slice index；
切片对应的运营商定义的接入类型。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在相关方法的实施例中进行了详细描述，此处将不做详细阐述说明。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
下面结合特定的技术细节，概括地示例性说明根据本公开的具体的信息发送方法和/或信息接收方法，如下：
为了解决在TA下不同小区支持不同切片或不同切片具有不同的首选频率/小区的部署场景下，由于UE当前驻留小区由于不支持某个切片导致切片对应的PDU session资源请求失败，进而导致UE此次PDU session建立请求被拒绝，或由于当前驻留频率/小区非切片首选，导致服务质量差等问题，考虑UE在发送PDU session建立请求时，同时在AS消息中指示PDU session对应的切片信息，用于辅助RAN判断是否支持/首选支持该切片，如果不是，则基于该切片信息将UE预切换到支持该切片的小区或该切片的首选频率/小区。
1.UE向基站上报NAS消息对应切片信息，基站接收并基于该切片信息进行预切换。
基于1，如果UE已知当前小区是否支持NAS消息对应切片，则只有在当前小区不支持该切片时，UE发送NAS消息时上报切片信息给基站。
基于1，如果基于现有标准，即UE未知当前小区是否支持NAS消息对应切片，则UE始终需要在发送NAS消息时上报切片信息给基站。
基于1-3中的任一项，所述NAS消息是PDU session建立请求。
基于1-3中的任一项，所述预切换，是指将UE切换到支持/首选支持该切片的小区。
基于1-3中的任一项，所述切片信息由UE NAS层确定并提供给AS层。
在一个实施例中：当UE有业务发起需要建立新的PDU session时，UE NAS层可以根据PCF提供或本地配置的URSP rule确定业务对应的S-NSSAI并提供给AS层。
基于1-3中的任一项，所述切片信息可以包含在Ulinformationtransfer或其他AS消息发送给基站。
在一个实施例中：UE NAS层在确定需要新建PDU session后，将PDU Session建立请求这一NAS消息与切片信息同时提供给AS层，由AS层一起封装在Ulinformationtransfer消息中发送给基站。
基于2,所述小区支持的切片信息可以由SIB消息或RRCRelease消息或NAS层提供。
基于1，基站在接收到UE上报的切片信息后，判断UE当前小区是否支持/首 选支持该切片，如果不支持或不首选支持该切片，则触发切换。
如果当前小区不支持，则一定执行切换，如果当前小区不首选支持，基站自行判断是否执行切换。
基于9，基站在触发切换的同时，可以继续转发该NAS消息给AMF，也可以将NAS消息缓存。
基于10，如果基站将该NAS消息缓存，基站将在切换完成之后发送该NAS消息给AMF。
在一个实施例中：
基站将PDU session建立请求缓存，并在Xn切换中当源基站收到目标基站的切换请求响应后通过Xn接口消息转发给目标基站，目标基站将PDU session建立请求与路径切换请求一起发送给AMF或在收到路径切换请求响应后单独发送给AMF。
基站将PDU session建立请求缓存，并在N2切换中当源基站收到AMF的UE上下文释放命令后单独封装到N2消息中发送给AMF，也可以与UE上下文释放命令完成消息一起发送给AMF。
基于10，如果基站在触发切换的同时继续转发该NAS消息，基站发送指示通知AMF当前基站正在做切换，AMF接收到指示后，暂缓该NAS消息对应流程，除非它检测到切换执行已经完成或切换失败/取消，则继续执行该NAS消息对应流程。
基于9，所述切换失败，可以由基站发送切换失败消息给AMF，也可以在AMF收到基站指示后，本地配置并激活定时器，定时器到期前没有检测到切换成功或取消则认为切换失败。
在一个实施例中：
对于Xn切换，基站可以在转发PDU session建立请求的N2消息中指示AMF此时基站正在做Xn切换，AMF接收到指示后，暂缓PDU session建立流程，同时设置并激活定时器，当AMF接收到源基站发送的切换取消请求(切换取消)或路径切换请求(切换成功)或切换失败消息或本地定时器到期(切换失败)，则继续执行PDU session建立流程。
对于N2切换，基站可以在包含PDU session建立请求的N2消息中指示基站正在做N2切换，也可以将Handover Required消息与PDU session建立请求一起发送到 AMF，当AMF同时收到Handover Required和PDU session建立请求时，暂缓PDU session建立流程，同时设置并激活定时器，当AMF收到目标基站发送的Handover Notify消息(切换成功)或源基站发送的切换取消请求(切换取消)或切换失败消息或本地定时器到期(切换失败)，则继续执行PDU session建立流程。
基于以上，所述切片信息可以是S-NSSAI,也可以是SST、slice index、运营商定义的接入类型或其他任何可以唯一指示切片的信息。
本公开的实施例还提出一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为实现上述信息发送方法和/或信息接收方法。
本公开的实施例还提出一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述信息发送方法和/或信息接收方法中的步骤。
如图10所示，图10是根据本公开的实施例示出的一种用于信息接收的装置1000的示意框图。装置1000可以被提供为一基站。参照图10，装置1000包括处理组件1022、无线发射/接收组件1024、天线组件1026、以及无线接口特有的信号处理部分，处理组件1022可进一步包括一个或多个处理器。处理组件1022中的其中一个处理器可以被配置为实现信息接收的方法。
图11是根据本公开的实施例示出的一种用于信息发送的装置1100的示意框图。例如，装置1100可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图11，装置1100可以包括以下一个或多个组件：处理组件1102，存储器1104，电源组件1106，多媒体组件1108，音频组件1110，输入/输出(I/O)的接口1112，传感器组件1114，以及通信组件1116。
处理组件1102通常控制装置1100的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件1102可以包括一个或多个处理器1120来执行指令，以完成上述的信息发送方法的全部或部分步骤。此外，处理组件1102可以包括一个或多个模块，便于处理组件1102和其他组件之间的交互。例如，处理组件1102可以包括多媒体模块，以方便多媒体组件1108和处理组件1102之间的交互。
存储器1104被配置为存储各种类型的数据以支持在装置1100的操作。这些数据的示例包括用于在装置1100上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1104可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1106为装置1100的各种组件提供电力。电源组件1106可以包括电源管理系统，一个或多个电源，及其他与为装置1100生成、管理和分配电力相关联的组件。
多媒体组件1108包括在所述装置1100和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1108包括一个前置摄像头和/或后置摄像头。当装置1100处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1110被配置为输出和/或输入音频信号。例如，音频组件1110包括一个麦克风(MIC)，当装置1100处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1104或经由通信组件1116发送。在一些实施例中，音频组件1110还包括一个扬声器，用于输出音频信号。
I/O接口1112为处理组件1102和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1114包括一个或多个传感器，用于为装置1100提供各个方面的状态评估。例如，传感器组件1114可以检测到装置1100的打开/关闭状态，组件的相对定位，例如所述组件为装置1100的显示器和小键盘，传感器组件1114还可以检测装置1100或装置1100一个组件的位置改变，用户与装置1100接触的存在或不存在，装 置1100方位或加速/减速和装置1100的温度变化。传感器组件1114可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1114还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1114还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1116被配置为便于装置1100和其他设备之间有线或无线方式的通信。装置1100可以接入基于通信标准的无线网络，如WiFi，2G或3G，4G LTE、5G NR或它们的组合。在一个示例性实施例中，通信组件1116经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1116还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1100可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述信息发送方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1104，上述指令可由装置1100的处理器1120执行以完成上述信息发送方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个 实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本公开实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本公开的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本公开的方法及其核心思想；同时，对于本领域的一般技术人员，依据本公开的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本公开的限制。

Claims (20)

  1. 一种信息发送方法，其特征在于，应用于终端，所述方法包括：
    确定发起的业务对应切片的切片信息；
    向第一基站发送所述切片信息；
    其中，所述切片信息用于供第一基站确定是否将所述终端切换到支持所述切片的第二基站。
  2. 根据权利要求1所述的方法，其特征在于，所述切片信息用于供所述第一基站在确定所述第一基站不支持所述切片的情况下，将所述终端切换到所述第二基站。
  3. 根据权利要求1所述的方法，其特征在于，所述切片信息用于供第一基站在确定所述第一基站不是首选支持所述切片的情况下，将所述终端切换至首选支持所述切片的第二基站。
  4. 根据权利要求1所述的方法，其特征在于，所述确定发起的业务对应切片的切片信息包括：
    响应于所述业务要发起，通过非接入层确定所述业务对应切片的切片信息；
    通过非接入层将所述切片信息发送至接入层。
  5. 根据权利要求1所述的方法，其特征在于，所述向第一基站发送所述切片信息，包括：
    在用于发送非接入层NAS消息的接入层AS消息中，携带所述切片信息。
  6. 根据权利要求1所述的方法，其特征在于，所述向第一基站发送切片的切片信息，包括：
    响应于确定所述第一基站不支持或确定所述第一基站不是首选支持所述切片，向所述第一基站发送所述切片信息。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    接收所述第一基站发送的系统消息SI或者无线资源控制消息RRC，其中，所述系统消息或者所述无线资源控制消息，携带有所述第一基站关于支持切片的能力信息；
    根据所述第一基站关于支持切片的能力信息确定所述第一基站是否支持或是否首选支持所述切片。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述切片信息为以下至少一个：
    切片的单一网络切片选择辅助信息S-NSSAI；
    切片的切片/服务类型SST；
    切片的切片索引slice index；
    切片对应的运营商定义的接入类型。
  9. 一种信息接收方法，其特征在于，应用于第一基站，所述方法包括：
    接收终端发送的与所述终端发起的业务对应切片的切片信息；
    根据所述切片信息确定是否将所述终端切换到支持所述切片的第二基站。
  10. 根据权利要求9所述的方法，其特征在于，所述根据所述切片信息确定是否将所述终端切换到支持所述切片的第二基站包括：
    响应于根据所述切片信息确定不支持所述切片，将所述终端切换到所述第二基站。
  11. 根据权利要求10所述的方法，其特征在于，所述响应于根据所述切片信息确定不支持所述切片，将所述终端切换到所述第二基站包括：
    响应于根据所述切片信息确定不是首选支持所述切片，将所述终端切换到首选支持所述切片的第二基站。
  12. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    接收并缓存所述终端发送的非接入层消息；
    响应于通过NG切换将所述终端切换到所述第二基站，将所述非接入层消息发送至核心网。
  13. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    接收并缓存所述终端发送的非接入层消息；
    响应于通过Xn切换将所述终端切换到所述第二基站，将所述非接入层消息发送至第二基站。
  14. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    接收终端发送的非接入层消息，并将所述非接入层消息发送至核心网；
    向所述核心网发送第一指示信息，其中，所述第一指示信息用于指示所述核心网在所述第一基站将所述终端切换到所述第二基站的动作结束之前，停止响应所述非接入层消息。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    响应于所述将所述终端切换到所述第二基站的动作结束，向所述核心网发送第二指示信息，其中，所述第二指示信息用于指示所述核心网继续响应所述非接入层消息。
  16. 根据权利要求9-15中任一项所述的方法，其特征在于，所述切片信息为以下至少一个：
    切片的S-NSSAI；
    切片的SST；
    切片的slice index；
    切片对应的运营商定义的接入类型。
  17. 一种信息发送装置，其特征在于，应用于终端，所述装置包括：
    信息确定模块，被配置为确定发起的业务对应切片的切片信息；
    信息发送模块，被配置为向第一基站发送所述切片信息；
    其中，所述切片信息用于供第一基站确定是否将所述终端切换到支持所述切片的第二基站。
  18. 一种信息接收装置，其特征在于，应用于第一基站，所述装置包括：
    信息接收模块，被配置为接收终端发送的与所述终端发起的业务对应切片的切片信息；
    切换模块，被配置为根据所述切片信息确定是否将所述终端切换到支持所述切片的第二基站。
  19. 一种电子设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为实现权利要求1至16中任一项所述的信息发送方法和/或信息接收方法。
  20. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现权利要求1至16中任一项所述的信息发送方法和/或信息接收方法中的步骤。
PCT/CN2021/073757 2021-01-26 2021-01-26 信息发送方法和装置、信息接收方法和装置 WO2022160090A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180000291.2A CN112913279B (zh) 2021-01-26 2021-01-26 信息发送方法和装置、信息接收方法和装置
PCT/CN2021/073757 WO2022160090A1 (zh) 2021-01-26 2021-01-26 信息发送方法和装置、信息接收方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/073757 WO2022160090A1 (zh) 2021-01-26 2021-01-26 信息发送方法和装置、信息接收方法和装置

Publications (1)

Publication Number Publication Date
WO2022160090A1 true WO2022160090A1 (zh) 2022-08-04

Family

ID=76109065

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/073757 WO2022160090A1 (zh) 2021-01-26 2021-01-26 信息发送方法和装置、信息接收方法和装置

Country Status (2)

Country Link
CN (1) CN112913279B (zh)
WO (1) WO2022160090A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114401535A (zh) * 2021-12-27 2022-04-26 中国电信股份有限公司 一种网络切片的切换方法、装置及电子设备
CN118044250A (zh) * 2021-12-31 2024-05-14 Oppo广东移动通信有限公司 信息上报方法、装置、设备、存储介质及程序产品
CN116567782A (zh) * 2022-01-27 2023-08-08 华为技术有限公司 基于切片的通信方法及其装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107708109A (zh) * 2016-08-08 2018-02-16 中兴通讯股份有限公司 业务处理方法、装置、系统、基站、终端及核心网网元
WO2018171904A1 (en) * 2017-03-24 2018-09-27 Huawei Technologies Co., Ltd. Devices and methods for slice-compliant handover control
CN108924884A (zh) * 2017-04-04 2018-11-30 华为技术有限公司 通信方法及通信设备
CN109309939A (zh) * 2017-07-28 2019-02-05 展讯通信（上海）有限公司 用户终端及其移动性管理方法、基站及可读存储介质
CN110708734A (zh) * 2019-10-12 2020-01-17 中国联合网络通信集团有限公司 一种切换的方法、网络设备、终端及切换系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110267327B (zh) * 2019-05-08 2021-04-27 中国联合网络通信集团有限公司 业务传输方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107708109A (zh) * 2016-08-08 2018-02-16 中兴通讯股份有限公司 业务处理方法、装置、系统、基站、终端及核心网网元
WO2018171904A1 (en) * 2017-03-24 2018-09-27 Huawei Technologies Co., Ltd. Devices and methods for slice-compliant handover control
CN108924884A (zh) * 2017-04-04 2018-11-30 华为技术有限公司 通信方法及通信设备
CN109309939A (zh) * 2017-07-28 2019-02-05 展讯通信（上海）有限公司 用户终端及其移动性管理方法、基站及可读存储介质
CN110708734A (zh) * 2019-10-12 2020-01-17 中国联合网络通信集团有限公司 一种切换的方法、网络设备、终端及切换系统

Also Published As

Publication number Publication date
CN112913279A (zh) 2021-06-04
CN112913279B (zh) 2023-11-14

Similar Documents

Publication Publication Date Title
WO2022160090A1 (zh) 信息发送方法和装置、信息接收方法和装置
US20220295590A1 (en) Inactivity timer control method and device
KR20100093344A (ko) 이동 단말기 및 이것의 핸드오버 방법
KR102358644B1 (ko) 서비스 처리 방법, 정보 송신 방법 및 관련 기기
CN109196909B (zh) 小区切换方法及装置
WO2023010400A1 (zh) 一种切换中继用户设备的方法、装置、设备及可读存储介质
WO2023279393A1 (zh) 信息发送、寻呼限制方法和装置、通信装置和存储介质
CN108702333B (zh) 一种数据传输方法和装置
WO2018201462A1 (zh) 一种通信方法及装置
CN109451788B (zh) 一种数据传输方法和装置
WO2022052070A1 (zh) 连接控制方法、连接控制装置
WO2022174393A1 (zh) 能力交互方法和装置、交互触发方法和装置
WO2022155935A9 (zh) 请求信息发送方法和装置、请求信息接收方法和装置
WO2022205203A1 (zh) 定位信息发送方法和装置、定位信息接收方法和装置
WO2022170457A1 (zh) 业务挂起方法和装置、挂起指示方法和装置
WO2023141828A1 (zh) 指示发送、接收方法和装置、通信装置和存储介质
WO2023000154A1 (zh) 跟踪区异常处理方法及装置、通信设备及存储介质
WO2023236019A1 (zh) 能力上报、能力确定方法和装置、通信装置及存储介质
WO2024031462A1 (zh) 通信控制方法、系统及装置、通信设备及存储介质
WO2022198399A1 (zh) 一种充电方法及装置
WO2024011528A1 (zh) 端口切换、端口切换指示方法和装置
WO2022227074A1 (zh) 指示收发方法、指示方法和响应确定方法
WO2022067559A1 (zh) 请求发送方法、响应信息发送方法、定位信息获取方法
WO2024040415A1 (zh) 通信控制方法、系统及装置、通信设备及存储介质
WO2023004602A1 (zh) 信息发送、寻呼限制方法和装置、通信装置和存储介质

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: 21921712

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21921712

Country of ref document: EP

Kind code of ref document: A1