Communication method and communication apparatus
By passing information indicating support from the first relay node between the core network device and the terminal device, the problem of low success rate of requesting network slicing services by terminal devices is solved, and a higher user experience is achieved.
Patent Information
- Application Number
- PCT/CN2024/086523
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-06
- Filing Date
- 2024-04-08
- Publication Date
- 2024-11-14
AI Technical Summary
In the prior art, the success rate of terminal devices when requesting network slicing services is low, resulting in poor user experience.
By passing specific information between the core network device and the terminal device, it is instructed to indicate the network slice supported by the first relay node, even if the slice is not supported by the second tracking area TA, so as to confirm the actual access network side in the core network device. Supports this slice service, and then includes the slice identifier in the returned NSSAI.
It improves the success rate of terminal devices requesting network slicing services and improves user experience.
Smart Images

Figure CN2024086523_14112024_PF_FP_ABST
Abstract
Description
Communication method and communication device
[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on May 6, 2023, with application number 202310506337.9 and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a communication method and a communication device. Background Art
[0003] The terminal device can include the slice identifier of the network slice service to be requested in the registration request message to request a specific slice service from the core network device. Accordingly, for the core network device, after receiving the registration request message containing the slice identifier, it is necessary to determine whether the access network side supports the slice service requested by the terminal device.
[0004] Currently, the implementation method for the core network device to determine whether the access network side supports the slice service requested by the terminal device is as follows: obtain the tracking area (TA) where the terminal device is located. Obtain the network slice list (slice list) supported by the TA reported by the access network side. Determine whether the slice identifier of the slice service requested by the terminal device is included in the slice list. If included, it is determined that the access network side supports the slice service requested by the terminal device; otherwise, it is determined that the access network side does not support the slice service requested by the terminal device.
[0005] However, the above method may have the problem of low success rate when the terminal device requests network slicing services.
[0006] Summary of the Invention
[0007] The present application proposes a communication method and a communication device to improve the success rate of terminal devices requesting network slicing services.
[0008] In a first aspect, the present application provides a communication method, which is applied to a core network device or a chip in a core network device, including: receiving first information from a terminal device, the first information is used to request a service corresponding to a first network slice, and the terminal device accesses a first relay node; receiving second information from a second host node, the second information is used to indicate that the first relay node supports the first network slice, the first network slice is not supported by a second tracking area TA, and when the host node of the first relay node is the second host node, the tracking area where the terminal device is located is the second TA; sending first allowed network slice selection auxiliary information NSSAI to the terminal device and / or the second host node, the first allowed NSSAI including an identifier of the first network slice.
[0009] In this implementation, the first network slice is supported by the first relay node but not by the second TA.
[0010] The second TA refers to the tracking area where the terminal device is located when the host node of the first relay node is the second host node.
[0011] The terminal device refers to a terminal device that is connected to the first relay node and remains relatively stationary with respect to the first relay node, and is also referred to as an on-board user equipment (UE).
[0012] In this implementation, when the host node of the first relay node is the second host node, the second host node will send second information to the core network device to indicate that the first relay node supports the first network slice, so that the core network device knows that the access network side (the second host node and the first relay node are both access network side devices) actually supports the services corresponding to the first network slice.
[0013] In a first implementation, when a terminal device requests a service corresponding to a first network slice, the second host node first determines that the first network slice is supported by the first relay node, and then sends a second message to the core network device to indicate to the core network device that the cell where the terminal device is located can support the first network slice. Accordingly, when the core network device receives the second message, it can directly determine that the access network side actually supports the service corresponding to the first network slice. It can be understood that when the second message adopts this form, it can be considered as an explicit indication method.
[0014] In a second implementation, when the host node of the first relay node changes from the first host node to the second host node, the second host node finds that the list of network slices supported by the first relay node is not exactly the same as the list of network slices supported by the second TA, and then sends a second message to the core network device. Specifically, the second message may include at least one of the following information: a first area identifier, a second area identifier, network slices supported by the first TA, and network slices supported by the second TA; wherein the first area identifier is used to indicate the first TA, the second area identifier is used to indicate the second TA, and when the host node of the first relay node is the first host node, the tracking area where the terminal device is located is the first TA, and the network slices supported by the first TA include the first network slice.
[0015] As an example of the second implementation method, when the core network device to which the first host node and the second host node belong is the same core network device, the second information may only include the first area identifier. It should be understood that in this example, since the first host node has previously reported the network slices supported by the first TA to the core network device, the core network device, after receiving the second information, can determine all network slices supported by the first TA as the network slices actually supported by the first relay node. Since all network slices supported by the first TA include the first network slice, the core network device can know that the first relay node actually supports the first network slice. Optionally, in this example, the second information sent by the first host node may also include any one or more of the following: the second area identifier, the network slices supported by the second TA, and the network slices supported by the first TA.
[0016] As another example of the second implementation method, when the core network device to which the first host node and the second host node belong is not the same core network device, wherein the core network device refers to a network element having core network side functions, such as a mobility management function (AMF). At this time, the second information may include: a first area identifier and the network slices supported by the first TA indicated by the first area identifier. In this example, for the core network device, after receiving the second information, all network slices supported by the first TA can be determined as network slices actually supported by the first relay node. Since the network slices supported by the first TA include the first network slice, the core network device can know that the first relay node actually supports the first network slice. Optionally, in this example, the second information sent by the first host node may also include any one or more of the following: a second area identifier, a network slice supported by the second TA.
[0017] In the prior art, when the host node of the first relay node accessed by the terminal device is the second host node, at this time, if the terminal device requests the service corresponding to the first network slice, then since the first network slice is not supported by the second TA, the core network device will think that the access network side does not support the first network slice, and thus when returning the allowed NSSAI (also called Allowed NSSAI) to the terminal device, the identifier of the first network slice will not be included in the Allowed NSSAI. However, in the technical solution provided by the present application, since the second host node sends the second information to the core network device to indicate that the first relay node supports the first network slice, the core network device can know that the access network side (the second host node and the first relay node are both access network side devices) actually supports the service corresponding to the first network slice. Therefore, when returning the Allowed NSSAI (that is, the first allowed NSSAI in this application, also referred to as the first Allowed NSSAI in this application) to the terminal device and / or the second host node, the identifier of the first network slice will be included in the Allowed NSSAI to indicate to the terminal device or the second host node that the service corresponding to the first network slice requested by the terminal device is allowed, thereby improving the success rate of the terminal device requesting the first network slice service, and thereby improving the user experience.
[0018] In combination with the first aspect, in a possible implementation manner, the first area identifier is a tracking area code TAC and / or a tracking area identifier TAI of a first TA, and the second area identifier is a TAC and / or TAI of a second TA.
[0019] In combination with the first aspect, in a possible implementation, the method further includes: sending third information to the terminal device, where the third information is used to indicate that the first network slice is supported by the first relay node.
[0020] In combination with the first aspect, in a possible implementation, the method also includes: receiving fourth information from the first host node, the fourth information is used to indicate that the first host node has established a protocol data unit PDU session for the terminal device; receiving fifth information from the first host node, the fifth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node; sending sixth information to the second host node, the sixth information is used to indicate that the second host node accepts the PDU session to be established indicated by the core network device, and the established PDU session includes the PDU session to be established.
[0021] The fifth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node. It can also be called: the fifth information is used to indicate that the terminal device is an on-board UE.
[0022] In one implementation, when the distance between the terminal device and the first relay node is less than a preset threshold, it is considered that the terminal device and the first relay node are relatively stationary.
[0023] In one implementation, the fifth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0024] In this implementation, because the first host node indicates to the core network device via the fifth information that the terminal device is an on-board UE, the core network device can determine the PDU session to be established and indicate to the second host node, where the PDU session to be established is a PDU session that does not require the second host node to perform handover admission control, thereby allowing the second host node to directly allocate resources for the PDU session to be established. It can be understood that the technical solution in this implementation ensures the continuity of the terminal device's PDU session, thereby improving the user experience.
[0025] In combination with the first aspect, in a possible implementation, the method further includes: sending a second allowed NSSAI to the second host node, where the second allowed NSSAI includes an identifier of the network slice associated with the PDU session to be established.
[0026] In the second aspect, the present application provides a communication method, which is applied to a terminal device or a chip in the terminal device, including: sending first information to a core network device, the first information is used to request a service corresponding to a first network slice, and the terminal device accesses a first relay node; receiving first allowed network slice selection auxiliary information NSSAI from the core network device, the first allowed NSSAI including an identifier of the first network slice; wherein, the first network slice is not supported by the second tracking area TA, and when the host node of the first relay node is the second host node, the tracking area where the terminal device is located is the second TA.
[0027] In combination with the second aspect, in a possible implementation, the method further includes: receiving third information from a core network device, wherein the third information is used to indicate that the first network slice is supported by a first relay node.
[0028] In combination with the second aspect, in a possible implementation, when the cell accessed by the terminal device changes from the first cell of the first relay node to the second cell, the method also includes: initiating a tracking area update TAU; wherein, the first cell and the second cell of the first relay node are located in the same registration area RA, and the second cell does not belong to the first relay node.
[0029] One implementation of initiating a tracking area update TAU includes: initiating the TAU when the system message broadcast by the second cell does not indicate that the second cell is the cell of the first relay node.
[0030] It should be understood that after the terminal device accesses the first cell of the first relay node, the following scenario may exist: as the terminal device moves, the cell accessed by the terminal device changes from the first cell to other cells that are not the first relay node. In this case, if the service corresponding to a slice requested by the terminal device is supported by the TA to which the second cell belongs but cannot be supported by the first relay node, the service corresponding to the slice requested by the terminal device should not be rejected. Therefore, in this implementation, when the cell accessed by the terminal device changes from the first cell of the first relay node to the second cell, the terminal device will initiate a TAU so that the terminal device can re-initiate the service corresponding to the network slice that was rejected in the cell of the first relay node but can be supported by the TA to which the second cell belongs within the RA.
[0031] In a third aspect, the present application provides a communication method, which is applied to a second host node or a chip in the second host node, including: sending second information to a core network device, the second information is used to indicate that the first relay node supports the first network slice, and the first network slice is not supported by the second tracking area TA; receiving first allowed network slice selection auxiliary information NSSAI from the core network device, the first allowed NSSAI including an identifier of the first network slice; wherein, the service corresponding to the first network slice is the service requested by the terminal device to the core network device, the terminal device accesses the first relay node, and when the host node of the first relay node is the second host node, the tracking area where the terminal device is located is the second TA.
[0032] In combination with the third aspect, in a possible implementation method, the second information includes at least one of the following information: a first area identifier, a second area identifier, a network slice supported by the first TA, and a network slice supported by the second TA; wherein, the first area identifier is used to indicate the first TA, the second area identifier is used to indicate the second TA, when the host node of the first relay node is the first host node, the tracking area where the terminal device is located is the first TA, and the network slices supported by the first TA include the first network slice.
[0033] In combination with the third aspect, in a possible implementation manner, the first area identifier is a tracking area code TAC and / or a tracking area identifier TAI of a first TA, and the second area identifier is a TAC and / or TAI of a second TA.
[0034] In combination with the third aspect, in a possible implementation, the method also includes: receiving sixth information from the core network device, the sixth information is used to indicate that the second host node accepts the protocol data unit PDU session to be established indicated by the core network device, and the PDU session established by the first host node for the terminal device includes the PDU session to be established; and determining to receive the PDU session to be established.
[0035] In combination with the third aspect, in a possible implementation, the method further includes: receiving a second allowed NSSAI from a core network device, wherein the second allowed NSSAI includes an identifier of a network slice associated with the PDU session to be established.
[0036] In a fourth aspect, the present application provides a communication method, which is applied to a first host node or a chip in the first host node, including: sending fourth information to a core network device, the fourth information being used to indicate that the first host node has established a protocol data unit (PDU) session for a terminal device; and sending fifth information to the core network device, the fifth information being used to indicate that the terminal device is connected to a first relay node and is relatively stationary with respect to the first relay node.
[0037] In combination with the fourth aspect, in a possible implementation method, the fifth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0038] In the fifth aspect, the present application provides a communication method, which is applied to a core network device, including: receiving fourth information sent from a first host node, the fourth information is used to indicate that the first host node has established a protocol data unit PDU session for the terminal device; receiving fifth information from the first host node, the fifth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node; sending sixth information to the second host node, the sixth information is used to indicate that the second host node accepts the PDU session to be established indicated by the core network device, and the established PDU session includes the PDU session to be established.
[0039] In combination with the fifth aspect, in a possible implementation, the method further includes: sending a second allowed NSSAI to the second host node, where the second allowed NSSAI includes an identifier of the network slice associated with the PDU session to be established.
[0040] In combination with the fifth aspect, in a possible implementation method, the fifth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0041] In a sixth aspect, the present application provides a communication method, which is applied to a first host node or a chip in the first host node, including: sending seventh information to a second host node, the seventh information being used to request the second host node to accept the protocol data unit PDU session established by the first host node for the terminal device, the seventh information including a session identifier associated with the established PDU session and an identifier of the network slice; sending eighth information to the second host node, the eighth information being used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node.
[0042] The eighth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node, which can also be called: the eighth information is used to indicate that the terminal device is an on-board UE.
[0043] In one implementation, the eighth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0044] In this implementation, because the first host node indicates to the second host node via the eighth information that the terminal device is an on-board UE, the second host node can determine that it is not necessary to perform admission control for the handover of the on-board UE, and thus directly allocate resources to the PDU session already established by the terminal device. It can be understood that the technical solution in this implementation ensures the continuity of the PDU session already established by the terminal device, thereby improving the user experience.
[0045] In the seventh aspect, the present application provides a communication method, which is applied to a second host node or a chip in the second host node, including: receiving seventh information sent from the first host node, the seventh information is used to request the second host node to accept the protocol data unit PDU session established by the first host node for the terminal device, and the seventh information includes the session identifier associated with the established PDU session and the identifier of the network slice; receiving eighth information from the first host node, the eighth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with the first relay node; and determining to accept the established PDU session.
[0046] In combination with the seventh aspect, in a possible implementation method, the eighth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0047] In combination with the seventh aspect, in a possible implementation, the method also includes: receiving third allowed network slice selection auxiliary information NSSAI from the core network device, the third allowed NSSAI including an identifier of the network slice associated with the established PDU session.
[0048] In an eighth aspect, the present application provides a communication method, which is applied to a first host node or a chip in the first host node, including: determining that a terminal device accessing a first relay node has established a protocol data unit PDU session, the host node of the first relay node is the first host node and the first relay node is deployed in a mobile device and moves with the mobile device; sending a ninth information to the first relay node, the ninth information being used to instruct the first relay node to prohibit updating the tracking area code TAC.
[0049] It should be noted that the TAC described in this application can also be replaced by a tracking area identifier TAI.
[0050] An implementation method of sending the ninth information to the first relay node includes: sending the ninth information to the first relay node when the network slice associated with the established PDU session is not supported by the second TA.
[0051] In combination with the eighth aspect, in a possible implementation manner, the ninth information is further used to indicate a duration for prohibiting updating the TAC in the first relay node.
[0052] The communication method provided by this implementation method, when the first host node determines that a PDU session has been established for the terminal device, instructs the first relay node to prohibit updating the TAC, so that the first relay node does not update the TAC, thereby ensuring that the established PDU session is not interrupted, thereby improving the user experience.
[0053] In one implementation, the ninth information includes the TAC of the second TA, where the second TA is the tracking area where the terminal device is located when the host node of the first relay node is the second host node.
[0054] In a ninth aspect, the present application provides a communication method, which is applied to a terminal device or a chip in a terminal device, and the method includes: when the cell in which the terminal device resides or accesses changes from a second cell to a first cell of a first relay node, prohibiting the sending of a tracking area update TAU; wherein, the second cell does not belong to the first relay node, and can be a stationary cell on the ground, the first relay node is deployed in the mobile device and moves with the mobile device, and the terminal device is not stationary relative to the first relay node.
[0055] Specifically, the terminal device in this implementation method refers to a terminal device that resides or accesses the first cell of the first relay node due to the mobility of the mobile device, but previously resided or accessed the second cell of other non-first relay nodes, also known as a non-following user device, or a surrounding user device (surrounding UE).
[0056] In combination with the ninth aspect, in a possible implementation method, the sending of tracking area update TAU is prohibited, including: when a system message broadcast by the first cell is received, the sending of TAU is prohibited, and the system message broadcast by the first cell includes indication information for indicating that the first cell is a cell of the first relay node and the TAC to which the first cell belongs.
[0057] In combination with the ninth aspect, in a possible implementation method, sending tracking area update TAU is prohibited, including: receiving the tenth information sent by the core network device, the tenth information is used to indicate the tracking area code TAC list of the relay nodes near the terminal device and / or the cell list of the relay nodes near the terminal device; when the TAC to which the first cell belongs or the cell identifier of the first cell is included in the content indicated by the tenth information, sending TAU is prohibited.
[0058] In combination with the ninth aspect, in a possible implementation method, sending a tracking area update TAU is prohibited, including: receiving a registration area RA sent by a core network device, the RA including a TAC list of relay nodes near the terminal device and / or a cell list of relay nodes near the terminal device; when it is determined that the TAC to which the first cell belongs or the cell identifier of the first cell is in the RA, sending TAU is prohibited.
[0059] The communication method provided by this implementation reduces the problem of the surrounding UE frequently initiating TAU due to the movement of the first relay node, which not only improves the user experience but also reduces unnecessary power consumption of the surrounding UE.
[0060] In the tenth aspect, the present application provides a communication device comprising: a memory and a processor; the memory is used to store program instructions; the processor is used to call the program instructions in the memory to execute the method described in any one of the first to ninth aspects or any possible implementation thereof.
[0061] In the eleventh aspect, the present application provides a computer-readable medium, which stores a program code for computer execution, and the program code includes instructions for executing the method described in any one of the first to ninth aspects or any possible implementation thereof.
[0062] In the twelfth aspect, the present application provides a computer program product, which includes a computer program code. When the computer program code is run on a computer, the computer implements the method described in any one of the first to ninth aspects or any possible implementation thereof.
[0063] Among them, the technical effects brought about by any implementation method in the tenth to twelfth aspects can be referred to the technical effects brought about by the above-mentioned first to third aspects and any possible implementation method therein, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0064] FIG1 is a schematic diagram of a communication system provided by this application;
[0065] FIG2 is a schematic diagram of an IAB architecture provided by this application;
[0066] FIG3 is a schematic diagram of a host change of an mAB node provided by the present application;
[0067] FIG4 is a schematic diagram showing a host change of another mAB node provided by the present application;
[0068] FIG5 is a schematic diagram of a method for improving the success rate of services corresponding to network slices requested by terminal devices, provided by one embodiment of the present application;
[0069] FIG6 is a schematic diagram of a method for improving the success rate of a service corresponding to a network slice requested by a terminal device, provided by another embodiment of the present application;
[0070] FIG7 is a schematic diagram of a communication method for managing a PDU session provided by one embodiment of the present application;
[0071] FIG8 is a schematic diagram of a communication method for managing PDU sessions provided in another embodiment of the present application;
[0072] FIG9 is a schematic diagram of a process for uninterrupted slicing services of an on-board UE provided by an embodiment of the present application;
[0073] FIG10 is a schematic diagram of a process for reducing the frequent TAU initiation by a surrounding UE according to an embodiment of the present application;
[0074] FIG11 is a schematic structural diagram of a communication device provided in one embodiment of the present application;
[0075] FIG12 is a structural diagram of a communication device provided in yet another embodiment of the present application. DETAILED DESCRIPTION
[0076] To facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. For example, the first information and the second information are used to distinguish different information and do not limit their order. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity or execution order, and words such as "first" and "second" do not necessarily mean that they are different.
[0077] It should be noted that, in this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.
[0078] In addition, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.
[0079] Below, the embodiments of the present application are described in detail with reference to the accompanying drawings.
[0080] To facilitate understanding, the following is a brief introduction to the terms involved in the embodiments of this application.
[0081] 1. Network Slice (Slice for short)
[0082] With hundreds of billions of IoT devices connected to the internet, different application scenarios are placing varying, sometimes even conflicting, demands on the network. Providing services for these diverse applications simultaneously through a single network can lead to an extremely complex network architecture, low network management efficiency, and inefficient resource utilization.
[0083] Network slicing technology provides isolated network environments for different application scenarios by creating virtual independent logical networks on the same network infrastructure, allowing different application scenarios to customize network functions and features according to their respective needs, and can effectively guarantee the QoS requirements of different services.
[0084] The goal of network slicing is to organically combine terminal devices, access network resources, core network resources, and network operation and maintenance and management systems to provide independent, isolated, and complete networks for different business scenarios or service types. Various scenarios have put forward different requirements for the 3rd Generation Partnership Project (3GPP) ecosystem, such as billing, policy, security, mobility, etc. 3GPP emphasizes that network slices should not affect each other. For example, a sudden large number of meter reading services should not affect normal mobile broadband services. In order to meet diverse needs and isolate slices, relatively independent management and operation of services are required, and customized service functions and analysis capabilities should be provided. Instances of different types of services are deployed on different network slices, and different instances of the same service type can also be deployed on different network slices.
[0085] When network slicing is deployed in the core network, the initial connection of a user to the network triggers the network slice selection process. This process considers parameters such as the user's subscription data, local configuration information, roaming agreement, and operator policies. This comprehensive consideration enables the selection of the appropriate slice type for the terminal device.
[0086] In the embodiment of the present application, network slices can be referred to as slices.
[0087] 2. Network Slice Identification
[0088] Single network slice selection assistance information (S-NSSAI) is used to identify a single network slice. S-NSSAI includes a slice type / service type (SST) and a slice differentiator (SD). SST is used to describe the characteristics and service features of a network slice, while SD is used to distinguish different network slices with the same SST characteristics.
[0089] Network slice selection assistance information (NSSAI) is a set of S-NSSAIs that are used to identify one or more network slices.
[0090] The network configures the NSSAI for the terminal device to use. After receiving this configuration parameter, the terminal device knows which S-NSSAI(s) are available on the network. The network side will indicate this to the terminal device through the "Configured NSSAI" information element (IE) in the registration accept message. If the terminal device configuration changes after registration, the network side can notify the terminal device to update it through the Configuration Update Command. The terminal device stores the Configured NSSAI configured by each network in non-volatile storage space. Each public land mobile network (PLMN) can only be configured with a maximum of one Configured NSSAI.
[0091] 4. Requested NSSAI
[0092] Allowed NSSAI or Configured NSSAI carried by the terminal device in the Registration Request message.
[0093] 5. Allowed NSSAI
[0094] Indicates which S-NSSAI(s) among the NSSAIs requested by the terminal device are allowed by the network side (including the access network side and the core network side). Specifically, the network side will indicate this to the terminal device through the "Allowed NSSAI" IE in the registration accept message.
[0095] 6.TA Update
[0096] When a terminal device registers with the network, the core network assigns a registration area (RA) to each terminal device. The RA contains a tracking area identity (TAI) list, where the TAI consists of a PLMN and a tracking area code (TAC).
[0097] When the terminal device is in idle state (also called IDLE state), in order to find the terminal device, the network side needs the core network to send paging messages (5GC paging) to all cells under all TAs in the TAI list, which is also called core network-level terminal device tracking.
[0098] When the terminal device moves to a cell that does not belong to the TAI list, that is, the cell where the terminal device is located is not in the area included in the RA, the terminal device will actively initiate a tracking area update (TAU). Then, after receiving the TAU, the core network device will register the location of the terminal device and update the RA of the terminal device to reassign the TAI list containing the TA to which the terminal device is currently located to the terminal device.
[0099] 7. The core network device obtains the slices supported by the access network side
[0100] The slice list supported by the access network device is pre-configured by the operation administration and maintenance (OAM) according to the TA granularity, and can then be reported to the core network device when establishing the NG interface with the core network device. That is, the access network side's support for slices is in line with the TA homogeneous deployment, and all cells within a specific TA support the same slices. If the access network device can also support centralized unit (CU) / distributed unit (DU) separation, further, the DU needs to first send the slice list supported by each TA to the CU, and then the CU reports it to the core network device.
[0101] Figure 1 is a schematic diagram of the architecture of a communication system 1000 used in an embodiment of the present application. As shown in Figure 1 , the communication system includes a radio access network 100 and a core network 200. Optionally, the communication system 1000 may also include the Internet 300. The radio access network (RAN) 100 may include at least one RAN node (such as 110a and 110b in Figure 1 , collectively referred to as 110), and may also include at least one terminal (such as 120a-120j in Figure 1 ). The terminal is connected to the radio access network device wirelessly, and the radio access network device is connected to the core network device wirelessly or by wire. The core network device and the radio access network device may be independent and distinct physical devices, or the functions of the core network device and the logical functions of the radio access network device may be integrated into the same physical device, or a single physical device may integrate some of the functions of the core network device and some of the functions of the radio access network device. Terminals and radio access network devices may be connected to each other by wire or by wireless. FIG1 is only a schematic diagram. The communication system may further include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in FIG1 .
[0102] The RAN 100 may be a 3GPP-related cellular system, such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.
[0103] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and facilitates wireless access for terminals. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal 120j accessing RAN 100 via network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functionality, and network elements 120a-120j can be understood as communication devices with terminal functionality.
[0104] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station (such as 110a in FIG1 ), a micro base station or an indoor station (such as 110b in FIG1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, a RAN node may also be a server, a wearable device, a vehicle or an onboard device. For example, an access network device in vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in this application may also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The RAN node in this application may also be a logical node, a logical module or software that can implement all or part of the RAN node functions.
[0105] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).
[0106] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0107] A terminal is a device with wireless transceiver capabilities that can send signals to a base station or receive signals from a base station. A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. A terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal.
[0108] Base stations and terminals can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.
[0109] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. To terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station. However, to base station 110a, 120i is a terminal, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with base station functionality, while 120a-120j in Figure 1 can be referred to as communication devices with terminal functionality.
[0110] Communication between base stations and terminals, between base stations, and between terminals can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.
[0111] In the embodiments of the present application, the functions of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem that includes the base station functions. The control subsystem that includes the base station functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal may also be performed by a module (such as a chip or modem) in the terminal, or by a device that includes the terminal functions.
[0112] Typically, in the communication system shown in FIG1 , a terminal device may include a slice identifier of a requested network slice service in a registration request message to request a specific slice service from a core network device. However, current terminal devices may have a low success rate when requesting network slice services from core network devices.
[0113] For example, when the communication system of Figure 1 adopts the IAB architecture, if the IAB node accessed by the terminal device is deployed on a mobile device (such as a vehicle) and moves with the mobile device, if the host node of the accessed IAB node changes, there may be a problem of a decrease in the success rate of slice service requests from terminal devices that have remained relatively stationary with the accessed IAB node.
[0114] For ease of understanding, the following describes in detail the problem of low success rate of slice service requests by terminal devices under the IAB architecture with reference to FIG. 2 and FIG. 4 .
[0115] First, a schematic diagram of an IAB architecture is described with reference to Figure 2. As shown in Figure 2, the IAB architecture includes a terminal device 201 (i.e., UE 201 in the figure), an IAB node 202, an IAB node 203, an IAB host 204, and a core network 205. The IAB host 204 is directly connected to the core network 205, and is connected to the IAB node 203, which is connected to the IAB node 202, which is connected to the terminal device 201. The physical interface between the terminal device 201 and the IAB node 202 is a Uu interface, and the physical interface between the IAB host 204 and the core network 205 is an NG interface.
[0116] As shown in Figure 2, the terminal device 201 can access the IAB node 202 through the Uu interface. The service data of the terminal device 201 can be transmitted through the IAB node 203 connected to the IAB node 202 to the IAB host 204 connected to the IAB node 203, and further transmitted to the core network through the NG interface between the IAB host 204 and the core network 205.
[0117] It should be understood that the embodiment of the present application does not specifically limit the names of the physical interfaces between the IAB node 202 and the IAB node 203 , and between the IAB node 203 and the IAB host 204 .
[0118] It should be understood that in the embodiments of the present application, the IAB host 204 can be connected to multiple IAB nodes, and each IAB node can also be connected to other IAB nodes or terminal devices. As an example, Figure 2 only shows one IAB node 203 connected to the IAB host 204, and also only shows one IAB node 202 connected to the IAB node 203, and one terminal device 201 connected to the IAB node 202, but it does not constitute a limitation on the embodiments of the present application.
[0119] In an embodiment of the present application, the IAB host and the IAB node may be devices for communicating with a mobile station, specifically, an access point (AP) in a wireless local area network (WLAN), a base transceiver station (BTS) in a global system for mobile communication (GSM) or code division multiple access (CDMA), a base station (nodeB, NB) in a wideband code division multiple access (WCDMA), an evolved base station (eNB) in an LTE system, a relay station or access point, an in-vehicle device, a wearable device, an access network device in a future 5G network, and an access network device in a future evolved public land mobile network (PLMN), etc.
[0120] The concept of the terminal device can be referred to the description of the terminal part in Figure 1, which will not be repeated here.
[0121] Specifically, in the IAB architecture, each IAB node is used to provide access and backhaul services for sub-nodes or terminal devices.
[0122] Specifically, each IAB node needs to maintain a wireless link with its parent node and also with its child nodes. If an IAB node's child node is a terminal device, the wireless link between the IAB node and the child node (i.e., the terminal device) is called a wireless access link. If an IAB node's child node is another IAB node, the wireless link between the IAB node and the child node (i.e., the other IAB node) is called a wireless backhaul link.
[0123] Taking FIG2 as an example, terminal device 201 accesses IAB node 202 via a wireless access link, IAB node 202 is connected to IAB node 203 via a wireless backhaul link, and IAB node 203 is connected to the IAB host via a wireless backhaul link.
[0124] It should be noted that, in the embodiment of the present application, the IAB node to which the terminal device is connected is also referred to as an access IAB node, and other IAB nodes for providing backhaul services other than the access IAB node are also referred to as intermediate IAB nodes.
[0125] Taking Figure 2 as an example, IAB node 202 is the access IAB node, and IAB node 203 is the intermediate IAB node. However, it should be understood that an IAB node is an access IAB node for terminals accessing that IAB node, and an intermediate IAB node for terminals accessing other IAB nodes. Therefore, whether an IAB node is an access IAB node or an intermediate IAB node is not fixed and depends on the specific application scenario.
[0126] More specifically, as shown in Figure 2, each IAB node consists of a mobile terminal (MT) part and a distributed unit (DU) part. When the IAB node faces its parent node, it can act as a terminal device, that is, the role of MT; when the IAB node faces its child node (the child node may be another IAB node or a terminal device), it is regarded as a network device, that is, it acts as a DU.
[0127] Taking Figure 2 as an example, when IAB node 202 faces its parent node (i.e., IAB node 203), it is considered a terminal device, i.e., the MT role. However, when IAB node 202 faces its child node (i.e., terminal device 201), it is considered a network device, i.e., the DU role. Similarly, when IAB node 203 faces its parent node (i.e., IAB host 204), it is considered a terminal device, i.e., the MT role. However, when IAB node 203 faces its child node (i.e., IAB node 202), it is considered a network device, i.e., the DU role.
[0128] To put it another way, to the DU in IAB host 204, the MT in IAB node 203 is considered a terminal device, while to the MT in IAB node 203, the DU in IAB host 204 is considered a network device. Similarly, to the DU in IAB node 203, the MT in IAB node 202 is considered a terminal device, while to the MT in IAB node 202, the DU in IAB node 203 is considered a network device. Similarly, to the terminal device 201, the DU in IAB node 201 is considered a network device.
[0129] Specifically, in the present application, the IAB host 204 can be an access network element with complete base station functions or an access network element with a separate centralized unit (CU) and a distributed unit (DU). In the present application, the centralized unit in the IAB host is also referred to as the Donor-CU (or simply CU), and the distributed unit in the IAB host is referred to as the Donor-DU. The Donor-CU may also be in a form with a separate control plane (CP) and user plane (UP). For example, the CU may be composed of a CU-CP and one or more CU-UPs.
[0130] As shown in Figure 2, the DU part of each IAB node is connected to the IAB host through the F1 interface. In addition, the MT in each IAB node can be connected to the Donor-CU through the air interface.
[0131] Specifically, the F1 interface includes a control plane and a user plane. The user plane is maintained between the DU of the IAB node and the Donor-CU-UP, while the control plane is maintained between the DU of the IAB node and the Donor-CU-CP.
[0132] Specifically, in this application, the core network 205 is mainly used to authenticate the terminal device, manage mobility, manage PDU sessions, etc. It should be noted that this application does not limit the specific form of the core network 205. For example, the core network 205 can be a fifth generation (5G) th The core network in the 5G (5th generation) mobile communication system, the core network in the 4G mobile communication system, the core network in the 6G mobile communication system, or the core network in the future communication system, etc.
[0133] More specifically, the core network 205 mainly includes the user plane function (UPF) of the data plane and the control plane function. Among them, the user plane function is mainly responsible for packet forwarding, quality of service (QoS) control, billing information statistics and connection to external networks, etc., which includes the relevant functions of the serving gateway (SGW) and public data network gateway (PDN-GW) of the long term evolution technology (LTE). The control plane function is mainly responsible for business process interaction, sending data packet forwarding strategies and QoS control strategies to the user plane. Exemplarily, the network elements in the control plane function mainly include: access and mobility function (AMF), session management function (SMF), policy control function (PCF), application function (AF), network exposure function (NEF), etc.
[0134] It should be understood that for the IAB architecture shown in Figure 2, the access IAB node (i.e., IAB node 202 in Figure 2) in the IAB architecture can be deployed on a mobile device (e.g., a vehicle) and move with the mobile device. During this movement, the host node of the access IAB node may change. In this application, for ease of description, the access IAB node that moves with the mobile device is also referred to as a mobile IAB (mIAB) node.
[0135] Exemplarily, with reference to FIG3 , a process leading to a possible change in the host node of an mAB node is described.
[0136] In the first possible scenario, the host node of the mAB node changes due to partial migration (also known as partial migration). As shown in Figure 3, when the mAB node is installed in a mobile device and moves with the mobile device, the MT in the mAB node (mIAB-MT in Figure 3) may switch from the cell controlled by Donor-DU1 to the cell controlled by Donor-DU2, while Donor-DU1 belongs to the topology controlled by CU1 and Donor-DU2 belongs to the topology controlled by CU2. It should be noted that in partial migration, only the mAB-MT handover is completed, that is, the radio resource control (RRC) connection of the mAB-MT is switched from CU1 to CU2, but the F1 connection of the mAB-DU2 is still terminated in CU1 and does not migrate to CU2 with the mAB node. At this time, CU1 is called F1-terminating Donor-CU and CU2 is called Non-F1-terminating Donor-CU.
[0137] In the second possible scenario, the host node of the mAB node changes due to DU migration (also known as DU migration). As shown in Figure 3, when the mAB node is installed in a mobile device and moves with the mobile device, the host node of the DU in the mAB node (mIAB-DU in Figure 3) may change from CU1 (source host) to CU3 (new host). Usually, the source host is also called the source F1-terminating Donor-CU, and the new host is also called the target F1-terminating Donor-CU.
[0138] Figure 3 is merely an example of how the host node of an mAB node may change. This figure does not necessarily require the first relay node to perform a partial migration followed by a DU migration. As long as the first relay node performs either partial migration or DU migration, it is considered that the host node of the mAB node may change.
[0139] Specifically, when performing DU migration, as shown in Figure 3, the mAB node can be considered to include two logical DUs, that is, the mAB-DU includes mAB-DU1 and mAB-DU2, which can be regarded as two different DUs, each with an F1 interface. Among them, mAB-DU1 has established a connection with CU1 through the F1 interface, and mAB-DU2 serves as the logical DU to be activated. During the movement, mAB-DU2 can be triggered by CU1 or OAM to establish a new F1 connection with CU3. It should be understood that after the mAB node completes DU migration, the cell where the terminal device resides or accesses needs to be changed from the cell managed by mAB-DU1 to the cell managed by mAB-DU2.
[0140] It should be noted that when DU migration is performed, this embodiment does not limit the specific form of the mAB-MT when it moves within the mAB node. For example, when the host of the DU in the mAB node changes from CU1 to CU3, the host of the mAB-MT is CU2. Optionally, when the host of the mAB-MT is CU2, CU2 and CU1 can also be the same CU, or CU2 and CU3 can also be the same CU.
[0141] Above, in conjunction with Figures 2 and 3, we introduced the concepts of changes in the IAB architecture and the host of the IAB node. Now, in conjunction with Figure 4, we analyze the problem of low success rate when terminal devices request network slicing services when the IAB host of the mIAB node changes.
[0142] For example, as shown in Figure 4, an mIAB node 403 is deployed on a vehicle and moves with the vehicle, and a terminal device 404 in the vehicle can access mIAB node 403. When the vehicle is in area 1, the IAB host of the DU in mIAB node 403 is IAB host 401. However, when the vehicle moves to area 2, the IAB host of the DU in mIAB node 403 becomes IAB host 402, that is, the IAB host of the DU in mIAB node 403 has migrated.
[0143] It should be understood that the terminal device 404 accessing the mAB node can include the slice identifier of the network slice service to be requested in the registration request message to request a specific slice service from the core network device. For the core network device, when it is determined that the current network side (including access network side support and core network side support) supports the service corresponding to the slice, the Allowed NSSAI is returned to the terminal device 404 and the slice identifier is included in the Allowed NSSAI.
[0144] For the example shown in Figure 4, it is assumed that when the network is planned and deployed, area 1 corresponds to the first TA, area 2 corresponds to the second TA, and the network slice list supported by the first TA (also referred to as slice list in this application) includes slice1 and slice2, and the slice list supported by the second TA includes slice2 and slice3.
[0145] Then, when the IAB host of the DU in the mAB node 403 is migrated from the IAB host 401 to the IAB host 402 and the TA in the mAB node 403 is updated from the first TA to the second TA, but the slice list supported by the mAB node 403 is still the slice list supported by the first TA (that is, the TA in the mAB node 403 is updated but the supported slice list is not updated), at this time, if the terminal device 404 requests the service corresponding to slice1 from the core network device, then since the slice list supported by the second TA does not include slice1, the core network device will think that the access network side does not support the service corresponding to slice1 (but the mAB node 403 actually supports it), which causes the terminal device 404 to fail when requesting the service corresponding to slice1, resulting in a poor user experience.
[0146] In view of this, the present application proposes a communication method and a communication device to enhance user experience.
[0147] In addition, before introducing the solution provided by this application, it should be emphasized that the IAB architecture shown in Figure 2 above is only a specific example of a relay networking architecture. When implementing the communication method provided by this application, the above IAB architecture can also be expanded to other types of relay networking architectures. In this case, the IAB node in Figure 2 is also referred to as a relay node, and the IAB host or IAB host base station is also referred to as a host node or host base station. This embodiment of the application does not specifically limit this.
[0148] The communication method provided by this application is described below.
[0149] Figure 5 is a flow chart of a communication method provided by an embodiment of the present application. Specifically, the method described in Figure 5 is a flow chart of a communication method for improving the success rate of a terminal device requesting a slice service.
[0150] As shown in FIG5 , the method may include: S501 , S502 and S503 .
[0151] S501, the terminal device sends the first information to the core network device. Correspondingly, the core network device receives the first information sent by the terminal device, and the first information is used to request the service corresponding to the first network slice.
[0152] Exemplarily, the first relay node in this embodiment is in the form of an IAB node, and the core network device is in the form of an AMF.
[0153] In this embodiment, the first relay node may be deployed in a mobile device (eg, a vehicle) and move along with the mobile device.
[0154] In this embodiment, the terminal device accesses the first relay node, and the current host node of the first relay node is the second host node.
[0155] The fact that the current host node of the first relay node is the second host node can also be expressed as: the first relay node is currently connected to the CU in the second host node.
[0156] In one example, the first relay node currently establishes an F1 connection with the second host node via an F1 interface. In other words, in this example, the second host node refers to a host node that currently establishes an F1 connection with the first relay node.
[0157] In this embodiment, the terminal device refers to a terminal device that is connected to the first relay node and remains relatively stationary with respect to the first relay node, also referred to as an on-board UE.
[0158] In this embodiment, when the terminal device accesses the first relay node and the host node of the first relay node is the second host node, the terminal device can request the core network device for a service corresponding to a certain network slice, for example, through a registration request (Registration Request) to request registration of the first network slice (also referred to as slice1 in this embodiment), or through a service request (Service Request) to request service data corresponding to the first network slice, or through a protocol data unit (PDU) session establishment request (for example, called PDU Session Establishment Request) to request establishment of a PDU session associated with the first network slice, which is not limited in this embodiment.
[0159] Among them, the concept of network slicing can be referred to the description in the relevant technology, which will not be repeated here.
[0160] S502, the second host node sends the second information to the core network device, and accordingly, the core network device receives the second information sent by the second host node; wherein, the first network slice is not supported by the second tracking area TA, and when the host node of the first relay node is the second host node, the tracking area where the terminal device is located is the second TA.
[0161] In this embodiment, when the host node of the first relay node is the second host node, the TA where the terminal device is located is called the second TA.
[0162] In this embodiment, the second TA does not support the first network slice, or it can also be expressed as: the first network slice does not belong to the second TA.
[0163] In this embodiment, the first relay node accessed by the terminal device supports the first network slice. That is, in this embodiment, the slice list actually supported by the first relay node is not exactly the same as the slice list supported by the second TA. For example, the slice list actually supported by the first relay node includes slice1 and slice2, while the slice list supported by the second TA includes slice3 and slice4.
[0164] It should be understood that in the prior art, when the host node of the first relay node accessed by the terminal device is the second host node, the terminal device is located in the second TA. At this time, if the terminal device requests the service of the first network slice, then since the first network slice is not supported by the second TA, the core network device will think that the access network side does not support the service corresponding to the first network slice, and thus include the identifier of the first network slice in the rejected NSSAI (also called Rejected NSSAI) returned to the terminal device.
[0165] However, it should be understood that in the present application, the first relay node to which the terminal device accesses actually supports the first network slice. Therefore, if the access network side is judged based on the slice list supported by the second TA to determine whether it supports the service corresponding to the first network slice, the returned Allowed NSSAI will have a low accuracy problem.
[0166] In view of this, in this embodiment, the second host node will also send second information to the core network device, and the second information is used to indicate to the core network device that the first relay node currently accessed by the terminal device supports the first network slice, that is, the second host node actually tells the core network device that the first relay node actually supports the first network slice.
[0167] It should be noted that this embodiment does not limit the method of triggering the second host node to send the second information to the core network device.
[0168] In the first implementation method, when the terminal device requests the service corresponding to the first network slice, the second host node first determines that the first network slice is supported by the first relay node, and then sends the second information to the core network device.
[0169] Specifically, when the first implementation method is implemented, the second information sent by the core network device may directly include the identifier of the first network slice requested by the terminal device, or the second information may include an identifier indicating support for Requested NSSAI, which is not limited in this embodiment. It can be understood that in this way, the second information can be considered as a direct indication method.
[0170] In a second implementation, when the host node of the first relay node is the second host node, the second host node determines whether the slice list supported by the first relay node is the same as the slice list supported by the second TA. If they are not exactly the same, it sends second information to the core network device.
[0171] Exemplarily, when the first relay node follows the movement of the mobile device and the host node of the first relay node changes from the first host node to the second host node, if the second host node determines that the slice list supported by the first relay node is not exactly the same as the slice list supported by the second TA, it sends second information to the core network device to indicate the slice list actually supported by the first relay node to the core network device. In this embodiment, the slice list actually supported by the first relay node includes the first network slice.
[0172] Specifically, when the second implementation is implemented, the second information sent by the second host node includes at least one of the following information: a first area identifier, a second area identifier, network slices supported by the first TA, and network slices supported by the second TA; wherein the first area identifier is used to indicate the first TA, the second area identifier is used to indicate the second TA, the first TA is the tracking area where the terminal device is located when the host node of the first relay node is the first host node, and the network slices supported by the first TA include the first network slice. It should be understood that in this embodiment, the network slices supported by the first TA can be considered as actually supported by the first relay node, or in other words, in this implementation, the second information can be considered as a form of implicit indication.
[0173] In this embodiment, the network slices supported by the first TA can be understood as the network slices included in the slice list supported by the first TA, and the network slices supported by the second TA can be understood as the slice list supported by the second TA. Therefore, the network slices supported by the first TA can also be replaced by the slice list supported by the first TA in this application, and the network slices supported by the second TA can also be replaced by the slice list supported by the second TA in this application.
[0174] As an example, when the core network devices to which the first host node and the second host node belong are the same core network device, the second information may only include the first area identifier. It should be understood that in this example, since the first host node has previously reported the slice list supported by the first TA to the core network device, the core network device, after receiving the second information, can determine all network slices included in the slice list supported by the first TA as the network slices actually supported by the first relay node. Since the slice list supported by the first TA includes the first network slice, the core network device can know that the first relay node actually supports the first network slice. Optionally, in this example, the second information sent by the first host node may also include any one or more of the following: the second area identifier, the network slices supported by the second TA (or replaced by the slice list supported by the second TA), and the network slices supported by the first TA (or replaced by the slice list supported by the first TA).
[0175] Exemplarily, the first area identifier is a tracking area code (TAC) and / or a tracking area identity (TAI) of a first TA, and the second area identifier is a TAC and / or TAI of a second TA.
[0176] In one implementation, when the core network device to which the first host node and the second host node belong is not the same core network device, the second information may include: the first area identifier, the network slices supported by the first TA indicated by the first area identifier (or replaced by the slice list supported by the first TA). It should be understood that in this example, for the core network device, after receiving the second information, all network slices included in the slice list supported by the first TA can be determined as the network slices actually supported by the first relay node. Since the slice list supported by the first TA includes the first network slice, the core network device can know that the first relay node actually supports the first network slice. Optionally, in this example, the second information sent by the first host node may also include any one or more of the following: the second area identifier, the network slices supported by the second TA (or replaced by the slice list supported by the second TA).
[0177] S503, the core network device sends the first allowed network slice selection auxiliary information NSSAI to the terminal device and / or the second host node, and the first allowed NSSAI includes the identifier of the first network slice.
[0178] In this embodiment, since the second host node indicates to the core network device through the second information that the first network slice is supported by the first relay node, the core network device can determine that the access network side supports the service corresponding to the first network slice, and then return the first allowed NSSAI (Allowed NSSAI) to the terminal device and / or the second host node, the first Allowed NSSAI will include the identifier of the first network slice to indicate to the terminal device or the second host node that the network side allows the service corresponding to the first network slice requested by the terminal device.
[0179] That is to say, in the communication method provided in this embodiment, since the second host node indicates to the core network device through the second information that the first relay node supports the first network slice, the core network device no longer determines whether the returned first Allowed NSSAI includes the identifier of the first network slice based on the network slices supported by the second TA, but instead determines whether the returned first Allowed NSSAI includes the identifier of the first network slice based on the network slices actually supported by the first relay node, thereby improving the success rate of the terminal device requesting the service corresponding to the first network slice, thereby improving the user experience.
[0180] It should be understood that when a terminal device requests a service corresponding to a certain network slice, for example, when requesting a service corresponding to a second network slice, the second network slice may not be supported by the first relay node. In view of this, as an optional embodiment, the communication method provided by the present application further includes: when the first relay node determines that the second network slice is not supported by the first relay node, the second information is not sent to the core network device. It can be understood that in this way, for the core network device, it will determine whether the first Allowed NSSAI sent to the terminal device and / or the second host node includes the identifier of the second network slice based on the network slices supported by the second TA.
[0181] The above, combined with the embodiment shown in Figure 5, describes: how to improve the success rate of the on-board UE requesting the service corresponding to the first network slice.
[0182] Below, for ease of understanding, a more specific embodiment is described in conjunction with Figure 6 to illustrate the specific implementation method of the success rate when the on-board UE requests the service corresponding to the first network slice (also called slice1).
[0183] In this embodiment, the case where the host node of the first relay node changes from the first host node to the second host node due to DU migration, the first host node and the second host node belong to the same core network device, the network slices supported by the first relay node when the host node of the first relay node is the first host node are slice1 and slice2, and the network slices supported by the second TA when the host node of the first relay node is the second host node are slice2 and slice3 is described as an example.
[0184] As shown in FIG6 , the method includes: S601 , S602 , S603 and S604 .
[0185] S601: The first relay node sends the updated TAC2 and the slice list supported by TA2 indicated by TAC2 to the second host node.
[0186] During the specific implementation of this embodiment, when the host node of the first relay node changes from the first host node to the second host node, and the first relay node updates the TAC from TAC1 to TAC2 corresponding to the current area of the network planning deployment, the first relay node sends the updated TAC2 and the slice list supported by TA2 indicated by TAC2 to the second host node.
[0187] Among them, TAC1 refers to the identifier of TA1 (i.e., the first TA in the embodiment shown in Figure 5) where the on-board UE is located when the host node of the first relay node is the first host node, and TAC2 refers to the identifier of TA2 (i.e., the second TA in the embodiment shown in Figure 5) where the on-board UE is located when the host node of the first relay node is the second host node.
[0188] During specific implementation, the TAC2 to which the current area belongs may be obtained by the first relay node from the first host node, the second host node or the OAM.
[0189] Illustratively, in a first implementation manner, the first host node obtains TAC2 to which the current area belongs from the second host node, and then notifies the DU in the first relay node.
[0190] For example, in the second implementation method, the MT in the first relay node receives the broadcast of the second host node, which carries the TAC of the service cell to which the first relay node accesses. The TAC carried in the broadcast is TAC2 belonging to the current area, so the DU in the first relay node can also know it.
[0191] Exemplarily, in the third implementation, the DU in the first relay node obtains the TAC to which the current area belongs, namely, TAC2, based on the OAM configuration.
[0192] It should be understood that in this step, the first relay node only updates the TAC from TAC1 to TAC2, but the slice list actually supported by it is not updated.
[0193] In this embodiment, the first relay node may obtain the slice list supported by TA2 from the first host node / the second host node / the OAM, and then send TAC2 and the slice list supported by TA2 to the second host node after obtaining the slice list supported by TA2.
[0194] It should be noted that, in this embodiment, although the first relay node sends the updated TAC2 and the slice list supported by TA2 to the second host node, the first relay node does not update the slice list it actually supports.
[0195] That is, in this embodiment, when the host node of the first relay node changes from the first host node to the second host node, the TAC of the first relay node will be updated to the TAC of TA2, but the slice1 and slice2 included in the supported slice list will not be updated to slice2 and slice3.
[0196] Optionally, the first relay node may also send a slice list supported by TAC1 and / or TA1 to the second host node.
[0197] It should be noted that this embodiment does not limit how the first relay node sends the updated TAC2 and the slice list supported by TA2 to the second host node.
[0198] For example, in one implementation, the first relay node sends the updated TAC2 and TA2 supported slice list to the second host node through the F1 establishment request of the F1 interface or the gNB-DU configuration update signaling.
[0199] S602: The second donor node sends TAC2, a slice list supported by TA2 indicated by TAC2, TAC1, and / or a slice list supported by TA1 indicated by TAC1 to the core network device.
[0200] It should be noted that this step is optional.
[0201] In specific implementation, the second host node can send TAC2, the slice list supported by TA2, the slice list supported by TAC1 and / or TA1 to the core network device through the NG-RAN configuration update signaling of the NG interface.
[0202] Optionally, the slice list indicated by TAC1 and / TA1 may also be obtained from the first host node.
[0203] Exemplarily, when the second host node sends TAC2, a slice list supported by TA2, and a slice list supported by TAC1 and / or TA1, an information element structure is as follows:
[0204] Among them, > indicates the next level of structure.
[0205] S603, the terminal device initiates a service request corresponding to slice 1 to the core network device.
[0206] The identifier of slice 1 is sent to the core network device via a non-access stratum (NAS) message.
[0207] S604, when the core network device determines that the cell currently accessed by the terminal device can support the service corresponding to slice1, the core network device sends RA and a first allowed NSSAI to the terminal device, wherein the first allowed NSSAI includes the identifier of slice1.
[0208] Specifically, there are two implementation schemes for the core network device to determine whether the cell currently accessed by the terminal device can support the service corresponding to slice1:
[0209] In the first implementation scheme, when the second host node reports the location information of the terminal device to the core network device, it can include both the updated TAC2 and the updated TAC1 in the location information. In this way, the core network device can determine that the terminal device is located in the cell of the first relay node, and the first relay node is located in TA2 and the first relay node actually supports the slice list supported by TA1. Then, it can be determined that the cell currently accessed by the terminal device can support the service corresponding to slice1 in combination with the slice list supported by the TA indicated by each TAC received by the NG interface.
[0210] In the present application, the cell of the first relay node is also referred to as the cell controlled by the first relay node.
[0211] More specifically, in this first implementation scheme, the core network device can determine that the cell currently accessed by the terminal device can support the service corresponding to slice1 in combination with the slice list supported by the TA indicated by each TAC received by the NG interface, including: the core network obtains the slice list supported by TA1 indicated by TAC1 from the slice list supported by the TA indicated by the received TAC, and then determines the slice list supported by TA1 indicated by TAC1 as the slice list supported by the first relay node. Since the slice list supported by TA1 includes the identifier of slice1, the core network device can determine that the cell currently accessed by the terminal device can support the service corresponding to slice1.
[0212] Optionally, the second host node may also indicate to the core network device that the cell currently accessed by the terminal device is the cell of the first relay node.
[0213] In the second implementation scheme, when the terminal device initiates a service request corresponding to slice1 to the core network device, as shown in S6031 in Figure 6, the identifier of slice1 can also be provided to the second host node through RRC. Then, when the second host node receives the identifier of slice1, the second host node executes S6032: sending indication information to the core network device to indicate that the cell currently accessed by the terminal device can support the service corresponding to slice1. Accordingly, for the core network device, after receiving the indication information, it can be known that the cell currently accessed by the terminal device can support the service corresponding to slice1.
[0214] In this embodiment, the core network device may further determine that the cell currently accessed by the terminal device is the cell of the first relay node. Specifically, the implementation method of the core network device determining that the cell currently accessed by the terminal device is the cell of the first relay node may include at least one of the following:
[0215] 1) The location information of the terminal device reported by the second host node includes both the updated TAC2 and the updated TAC1, so that the core network device can determine that the cell accessed by the terminal device is the cell of the first relay node.
[0216] 2) The core network device determines that the cell accessed by the terminal device is the cell of the first relay node based on the indication information sent by the second host node, which is used to indicate that the cell currently accessed by the terminal device is the cell of the first relay node.
[0217] 3) The core network device directly determines that the cell accessed by the terminal device can support the service corresponding to slice1 based on the indication information sent by the second host node to indicate that the cell currently accessed by the terminal device can support the service corresponding to slice1. However, the slice list supported by TAC2 and TA2 obtained from the NG interface message includes {slice2 and slice3}. The core network device can determine that the cell accessed by the terminal device is the cell of the first relay node.
[0218] In this embodiment, when sending the RA and the first allowed NSSAI to the terminal device:
[0219] In a first implementation, the first allowed NSSAI includes the identifier of slice1, and the RA includes TA2 identified by TAC2.
[0220] In the second implementation scheme, the first allowed NSSAI includes the identifier of slice1, and the RA includes TA1 identified by TAC1. However, it should be noted that in the second implementation scheme, the RA in the context of the terminal device actually stored by the AMF includes TA2 identified by TAC2.
[0221] Optionally, the core network device may also send the first allowed NSSAI to the second host node or request the second host node to establish a PDU session associated with the first network slice.
[0222] Optionally, based on the first implementation scheme and the second implementation scheme in this step, the core network device may further send a third information to the terminal device, wherein the third information is used to indicate that slice1 in the first allowed NSSAI is supported by the first relay node (also referred to as supported by the cell of the first relay node). It should be understood that since the cell accessed by the terminal device also broadcasts the indication information that the cell is the cell of the first relay node and the corresponding TAC, after receiving the third information, the terminal device can determine that the current access is to the cell controlled by the first relay node in TA2 and the first network slice in the first allowed NSSAI is supported by the cell.
[0223] In the communication method provided in this embodiment, when the host node of the first relay node changes from the first host node to the second host node, since the second host node reports the location information of the terminal device to the core network device, the reported location information also includes the identifier TAC1 of TA1 where the terminal device is located when the host node of the first relay node is the first host node and the identifier TAC2 of TA2 where the terminal device is located when the host node of the first relay node is the second host node, so that the core network device can determine that the cell accessed by the terminal device can support the service corresponding to slice1 based on the slice supported by TA1 received by the NG interface, or determine that the accessed cell can support the service of slice1 based on direct indication, and thus include the identifier of slice1 in the first allowed NSSAI sent, so that when the terminal device requests the service corresponding to slice1, the request is successful, thereby improving the user experience.
[0224] Optionally, in the present application, when the terminal device accessing the first relay node determines that it is an on-board UE and the accessed cell is still controlled by the first relay node, there is no need to perform TAU.
[0225] In addition, it should be understood that for a terminal device accessing the first relay node, as the terminal device moves, the terminal device may change from accessing the first cell of the first relay node to a second cell other than the first relay node. In this case, if the terminal device requests a slice that can be supported by the TA corresponding to the second cell, the slice should not be rejected.
[0226] In view of this, the communication method provided in the present application also includes: when the cell accessed by the terminal device changes from the first cell of the first relay node to the second cell, initiating a tracking area update TAU; wherein, the first cell and the second cell of the first relay node are located in the same registration area RA, and the second cell does not belong to the first relay node.
[0227] Specifically, initiating a tracking area update TAU includes: initiating a TAU when the system message broadcast by the second cell does not indicate that the second cell is a cell of the first relay node. It can be understood that in this embodiment, since the terminal device can learn from the third information sent by the core network device that the cell previously accessed was a cell controlled by the first relay node in TAC2, and the broadcast message of the second cell currently accessed does not indicate that the second cell is a cell of the first relay node, it can be determined that it is located in a cell other than the first relay node controlled in the RA, and a TAU needs to be executed so that the service corresponding to the network slice that was rejected in the cell of the first relay node but can be supported by the TA to which the second cell belongs can be initiated again in the RA.
[0228] Optionally, the third information sent by the core network device to the terminal device may also include a list of cells controlled by the first relay node. At this time, the terminal device may also obtain the identifier of the second cell from the broadcast message of the second cell, and then determine that the second cell is not included in the list of cells controlled by the first relay node. It determines that it is currently located in a cell other than the first relay node controlled by the RA, and needs to perform TAU so that it can re-initiate the network slicing request that was rejected in the cell of the first relay node within the RA.
[0229] As an optional embodiment, if the host node of the first relay node changes from the first host node to the second host node due to MT migration in the first relay node, and the first relay node updates the TAC from TAC1 to TAC2 corresponding to the current area of the network planning deployment, then in order to improve the success rate of the on-board UE requesting the service corresponding to the first network slice (also called slice1), at this time, for the embodiment shown in Figure 6, with S603 and S604 unchanged, S601 can be replaced by: the first relay node can send the updated TAC2 and the slice list supported by TA2 indicated by TAC2 to the first host node; S602 can be replaced by: the first host node sends TAC2, the slice list supported by TA2 indicated by TAC2, TAC1 and / or the slice list supported by TA1 indicated by TAC1 to the core network device.
[0230] The communication method for improving the success rate of a terminal device (on-board UE) requesting a slice service is described above in conjunction with FIG. 5 and FIG. 6 .
[0231] It should be understood that when the host node of the relay node accessed by the terminal device (on-board UE) changes from the first host node to the second host node, at this time, if the first host node has established a PDU session for the terminal device, the continuity of the PDU session established for the on-board UE should also be guaranteed to enhance the user experience.
[0232] In view of this, the present application provides two further embodiments to illustrate how to ensure the continuity of the PDU session established by the first host node for the terminal device when the host node of the first relay node changes from the first host node to the second host node.
[0233] Below, first, with reference to FIG7 , a first embodiment of the present application for ensuring the continuity of a PDU session established by a first host node for a terminal device is described.
[0234] As shown in FIG7 , the method for ensuring the continuity of the PDU session established by the first host node for the terminal device includes:
[0235] S701, the first host node sends fourth information and fifth information to the core network device, wherein the fourth information is used to indicate that the first host node has established a PDU session for the terminal device, and the fifth information indicates that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node.
[0236] In this embodiment, the terminal device initially accesses the cell of the first relay node and successfully establishes a PDU session associated with the network slice. As an example, in this embodiment, the network slice associated with the PDU session successfully established by the terminal device is slice2.
[0237] During the specific implementation of this embodiment, when the host node of the first relay node changes from the first host node to the second host node, and a relay node updates the TAC from TAC1 to TAC2 corresponding to the current area of the network planning deployment, the first host node will send the fourth information and the fifth information to the core network device.
[0238] Among them, TAC1 refers to the identifier of TA1 (i.e., the first TA in the embodiment shown in Figure 5) where the on-board UE is located when the host node of the first relay node is the first host node, and TAC2 refers to the identifier of TA2 (i.e., the second TA in the embodiment shown in Figure 5) where the on-board UE is located when the host node of the first relay node is the second host node.
[0239] The fifth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node, which can be considered as indicating that the terminal device is an on-board UE.
[0240] In one implementation, the fourth information and the fifth information may be carried in the same signaling or in different signalings. For example, the first donor node sends the fourth information and the fifth information to the core network device via a handover request signaling.
[0241] It should be noted that this embodiment does not limit the specific form of the fifth information.
[0242] For example, the fifth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node (that is, indicating that the source cell where the terminal device resides is the cell of the first relay node).
[0243] S702, after the core network device determines the PDU session to be established indicated to the second host node, it sends the sixth information to the second host node, and the sixth information is used to instruct the second host node to accept the PDU session to be established indicated by the core network device, wherein the PDU session to be established is a PDU session that does not require the second host node to perform switching admission control.
[0244] In this embodiment, the PDU session to be established is included in the established PDU session, or in other words, the established PDU session includes the PDU session to be established.
[0245] For example, in one possible scenario, the PDU session to be established is all the PDU sessions that the first host node has established for the terminal device.
[0246] Exemplarily, in another possible scenario, the PDU session to be established is a partial PDU session in an established PDU session.
[0247] In this embodiment, when the core network device sends the sixth information to the second host node, in one implementation, the core network device sends the sixth information to the second host node through switching request signaling, and the sixth information may include the session identifier associated with the PDU session to be established indicated by the core network device and the identifier of the network slice (slice2).
[0248] As an optional embodiment, the sixth information may include the fifth information, that is, the sixth information carries indication information for indicating that the terminal device is an on-board UE. In this way, when the second host node receives the sixth information, it can be learned that the terminal device is an on-board UE and then determine that handover admission control is not required.
[0249] Optionally, the core network device may send a second allowed NSSAI to the second host node, where the second allowed NSSAI includes an identifier of the network slice associated with the PDU session to be established.
[0250] S703: The second host node notifies the core network device that it has accepted the PDU session to be established indicated by the core network device.
[0251] Exemplarily, the second donor node notifies the core network device of the accepted PDU session to be established through handover request response signaling.
[0252] S704 , the core network device notifies the first donor node that the handover preparation is complete.
[0253] Exemplarily, the core network device notifies the first donor node that the handover preparation is completed through handover command signaling.
[0254] S705: The terminal device starts executing the switching process.
[0255] Specifically, the terminal device starts to execute the handover process, which means that the cell accessed by the terminal device becomes the cell of the first relay node when the first relay node is controlled by the second host node.
[0256] In the communication method provided in the present application, since the first host node indicates to the core network device through the fifth information that the terminal device is an on-board UE, the core network device can determine the PDU session to be established indicated to the second host node, wherein the PDU session to be established is a PDU session that does not require the second host node to perform switching admission control, thereby allowing the second host node to directly allocate resources for the PDU session to be established. It can be understood that through the technical solution in this implementation method, the continuity of the PDU session of the terminal device can be guaranteed, thereby improving the user experience.
[0257] 8 , a second embodiment of the present application for ensuring the continuity of a PDU session established by a first host node for a terminal device will be described.
[0258] As shown in FIG8 , the communication method provided in this embodiment includes:
[0259] S801, the first host node sends the seventh information and the eighth information to the second host node, wherein the seventh information is used to request the second host node to accept the PDU session established by the first host node for the terminal device, and the eighth information indicates that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node.
[0260] In this embodiment, the terminal device initially accesses the cell of the first relay node and successfully establishes a PDU session associated with the network slice.
[0261] During the specific implementation of this embodiment, when the host node of the first relay node changes from the first host node to the second host node, and the first relay node updates the TAC from TAC1 to TAC2 corresponding to the current area of the network planning deployment, the first host node will send the seventh information and the eighth information to the second host node.
[0262] In one implementation, the seventh information and the eighth information may be carried in the same signaling or in different signalings.
[0263] For example, the first donor node sends the seventh information and the eighth information to the second donor node through handover request signaling.
[0264] Among them, the eighth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node, which can be considered as indicating that: the terminal device is an on-board UE.
[0265] It should be understood that the eighth information described here has the same function as the fifth information in the embodiment shown in Figure 7. The only difference is that the seventh information and the eighth information are sent from the first host node to the second host node.
[0266] For example, the eighth information may have the following two forms:
[0267] The first form: indicates that the reason for the handover request is the migration of a distributed unit DU in the first relay node or the migration of a mobile terminal MT.
[0268] The second form: when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0269] S802: After the second host node directly determines to accept the PDU session established by the first host node for the terminal device, it indicates to the first host node that the PDU session established by the first host node for the terminal device has been accepted.
[0270] Specifically, in this step, the logic for the second host node to directly determine to accept the PDU session established by the first host node for the terminal device is as follows:
[0271] 1) When the eighth information is the first form in S801, the second host node can determine that the switching of the terminal device is triggered by DU migration or MT migration, and therefore can know that the terminal device is an on-board UE, thereby directly determining to accept the PDU session established by the first host node for the terminal device and allocate resources for the established PDU session.
[0272] 2) When the eighth information is the second form in S801, since the second host node can determine that the cell where the terminal device is currently located is also the cell of the first relay node, that is, the terminal device is in the cell of the first relay node before and after switching, it is determined that the terminal device is an on-board UE. Therefore, it can be directly determined to accept the PDU session established by the first host node for the terminal device and allocate resources for the established PDU session.
[0273] When indicating to the first host node that the PDU session established by the first host node for the terminal device has been accepted, one implementation method includes: the second host node indicates to the first host node through a switching request response signaling that the PDU session established by the first host node for the terminal device has been accepted.
[0274] S803: The second host node indicates to the core network device that the PDU session established by the first host node for the terminal device has been accepted.
[0275] Exemplarily, the second host node indicates to the core network device through path switching request signaling that the PDU session established by the first host node for the terminal device has been accepted.
[0276] S804, the core network device sends the third allowed NSSAI to the second host node, and the third allowed NSSAI includes the identifier of the network slice associated with the established PDU session.
[0277] Exemplarily, the core network device sends the third allowed NSSAI to the second donor node through path switch response signaling.
[0278] S805: The terminal device starts executing the switching process.
[0279] In the communication method provided by the present application, the first host node can send seventh information and eighth information to the second host node, wherein the seventh information is used to request the second host node to accept the PDU session established by the first host node for the terminal device, and the eighth information indicates that the terminal device is an on-board UE; accordingly, when the second host node receives the seventh information and the eighth information, it can determine that it is not necessary to perform admission control for the switching of the on-board UE and directly allocate resources for the PDU session established by the terminal device. It can be understood that through the technical solution in this implementation method, the continuity of the PDU session established by the terminal device can be guaranteed, thereby improving the user experience.
[0280] Optionally, for the embodiments shown in Figures 7 and 8, when the host node of the first relay node changes from the first host to the second host node, the second host node / core network device can also perform switching admission for the UE based on the slice list actually supported by the first relay node, that is, according to the existing technology, it is determined that the target cell can actually support the first network slice service, so the established PDU session associated with the first network slice can be admitted.
[0281] When the host node of the relay node accessed by the terminal device (on-board UE) changes from the first host node to the second host node, at this time, if the first host node has established a PDU session for the terminal device, it should ensure that the PDU session established for the on-board UE is not interrupted, so that the slice service associated with the PDU session is not interrupted, thereby improving the user experience.
[0282] In view of this, the present application provides an embodiment in combination with FIG9 , illustrating an embodiment provided by the present application for achieving uninterrupted PDU session established by the first host node for the terminal device.
[0283] As shown in FIG9 , the communication method includes:
[0284] S901, the terminal device accesses the cell of the first relay node and successfully establishes a PDU session associated with the network slice.
[0285] In this step, the current host node of the first relay node is the first host node. Exemplarily, in this embodiment, the network slice associated with the PDU session successfully established by the terminal device is slice2.
[0286] It should be noted that, in the present application, the cell in which the terminal device accesses the first relay node may also be referred to as the cell in which the terminal device accesses the first relay node, which does not constitute a limitation of the present application.
[0287] S902 : The host node of the first relay node changes from the first host node to the second host node.
[0288] S903: The first host node identifies the PDU session established by the terminal device.
[0289] S904: The first donor node sends ninth information to the first relay node. The ninth information is used to instruct the first relay node to prohibit updating the tracking area code TAC.
[0290] In one implementation, the first donor node may send ninth information to the mIAB-DU.
[0291] As an optional embodiment, in this embodiment, when the first host node identifies that a PDU session has been established for the terminal device, and further identifies that the network slice associated with the established PDU session is not supported by the second TA, it sends the ninth indication information to the second host node to instruct the first relay node to prohibit updating the TAC, wherein the second TA is the tracking area where the terminal device is located when the host node of the first relay node is the second host node.
[0292] In this embodiment, the ninth information can also be used to indicate the duration of the prohibition on TAC updates in the first relay node. It will be appreciated that in this implementation, upon receiving the ninth information, the terminal device not only knows that TAC updates need to be prohibited, but also knows the specific duration of the prohibition. In other words, after this duration has expired, the first relay node can update the TAC based on the network planning and deployment for the current region. Optionally, the ninth information can include the TAC for the current region.
[0293] It can be seen that in the communication method provided by the embodiment shown in Figure 9, when the first host node determines that the first relay node has allocated resources for the PDU session of the terminal device, such as establishing a corresponding data radio bearer (DRB), the first relay node is instructed to prohibit updating the TAC, so that the first relay node does not update the TAC, thereby achieving uninterrupted established PDU session and improving user experience.
[0294] Optionally, when the first relay node in the embodiment shown in Figure 9 is not updated according to the planned deployment of the TAC, it may also cause the surrounding UE to frequently initiate TAU (the first relay node moves to the vicinity of the surrounding UE, and the surrounding UE needs to perform TAU based on the TAC currently configured by the first relay node after accessing the cell of the first relay node. Then, when the first relay node moves out of the vicinity of the surrounding UE, the surrounding UE needs to perform TAU again based on the TAC of the current cell where it is stationed).
[0295] In view of this, the following, in conjunction with Figure 10, takes the case where the surrounding UE requests slice 3 supported by the second TA as an example to illustrate how to reduce the impact on the surrounding UE when the first relay node does not update the TAC to which it belongs according to the planned deployment. As shown in Figure 10, the method includes:
[0296] S100A, the terminal device accesses the second cell controlled by the second host node, and reports the service corresponding to slice 3 and its current location information to the core network device through the second host node.
[0297] Specifically, in this embodiment, the terminal device refers to (surrounding UE).
[0298] Then, for different types of surrounding UEs, there are two possible implementations:
[0299] The first implementation includes:
[0300] S100B, the core network device sends the allowed NSSAI and RA to the terminal device, wherein the allowed NSSAI includes the identifier of slice3, and the RA includes the TA identified by TAC2.
[0301] TAC2 refers to the identifier of the TA where the surrounding UE is located. In this embodiment, the TA where the surrounding UE is located is the second TA where the surrounding UE is located when the host node of the first relay node is the second host node.
[0302] During specific implementation, the core network device may send the allowed NSSAI and RA to the terminal device via a NAS message.
[0303] S100C, the first relay node moves to the vicinity of the terminal device, so that the cell where the terminal device resides or accesses is changed from the second cell to the first cell of the first relay node.
[0304] S100D: The second donor node broadcasts, in the first cell, indication information indicating that the cell is the cell of the first relay node, as well as the TAC and cell identifier to which the cell belongs.
[0305] S100E: The terminal device determines that the first cell in which it is currently located is the cell of the first relay node. Although the first cell is not within the RA, the terminal device is prohibited from sending a TAU.
[0306] The second implementation includes:
[0307] S100b, the core network device determines the TAC list of relay nodes that may pass near the terminal device and / or the cell list of relay nodes near the terminal device based on the current location of the terminal device and the OAM configuration information, and then sends a NAS message to the terminal device.
[0308] This embodiment takes the NAS message as a registration acceptance message as an example, but this does not constitute a limitation of the present application.
[0309] Specifically, in this step, the content carried has the following two possibilities:
[0310] The first form: the registration acceptance message includes a TAC list of relay nodes surrounding the UE and / or a cell list of relay nodes near the terminal device.
[0311] In specific implementation, it can be sent directly to the terminal device through a NAS message, or it can be sent to the second host node first and then sent to the terminal device by the second host node through an RRC message.
[0312] The second form: add the TAC list of the relay nodes passing by the determined surrounding UE and / or the cell list of the relay nodes near the terminal device to the RA configured for the UE, and then send the Allowed NSSAI and RA to the UE, where the Allowed NSSAI includes slice3, and the RA includes TA2 identified by TAC2 and TA1 identified by TAC1 and / or the cell identifier within TA1.
[0313] In this embodiment, TAC1 belongs to the TAC list of the relay node passing nearby, and the cell within TA1 identified by TAC1 belongs to the cell list of the relay node passing nearby.
[0314] S100c: The first relay node moves to the vicinity of the terminal device, so that the cell where the terminal device resides or accesses changes from the second cell to the first cell of the first relay node.
[0315] The first cell broadcasts indication information indicating that the first cell is a cell of the first relay node, and the TAC and cell identifier to which the cell belongs.
[0316] The indication information for indicating that the first cell is the first relay node may be considered as indicating that the first cell belongs to the first relay node.
[0317] S100d, the terminal device determines that sending TAU is prohibited.
[0318] For the first form in S110b, after the terminal device resides in or accesses the cell of the first relay node, it determines that the TAC or cell identifier of the cell of the first relay node is within the information pre-provided by the core network device, and therefore does not initiate a TAU request.
[0319] For the second form in S110b, after the terminal device resides in or accesses the cell of the first relay node, it determines that the TAC or cell identifier of the cell of the first relay node is within the RA, and therefore does not initiate a TAU request.
[0320] It should be understood that in the communication method provided in Figure 10, if the first relay node is providing slicing service for the on-board UE, the first host node instructs it not to temporarily update the TAC based on the local deployment, thereby ensuring the service continuity of the on-board UE, while reducing the surrounding UE from frequently initiating TAU due to the movement of mIAB, thereby reducing unnecessary power consumption of the surrounding UE.
[0321] In one implementation, the second implementation in the embodiment shown in FIG10 may be applicable to a case where the first relay node moves based on a fixed trajectory.
[0322] The communication method of the embodiment of the present application is described in detail above in conjunction with Figures 5 to 10. The communication device provided in the present application will be described in detail below in conjunction with Figures 11 and 10.
[0323] FIG11 is a schematic structural diagram of a communication device provided by an embodiment of the present application. Specifically, as shown in FIG11 , the device 1100 includes: a receiving module 1101 and a sending module 1102 .
[0324] In the first embodiment, the communication apparatus is applied to core network equipment.
[0325] The receiving module 1101 is used to receive first information from a terminal device, where the first information is used to request a service corresponding to a first network slice, and the terminal device accesses a first relay node; the receiving module 1101 is also used to receive second information from a second host node, where the second information is used to indicate that the first relay node supports the first network slice, the first network slice is not supported by the second tracking area TA, and when the host node of the first relay node is the second host node, the tracking area where the terminal device is located is the second TA; the sending module 1102 is used to send first allowed network slice selection auxiliary information NSSAI to the terminal device and / or the second host node, where the first allowed NSSAI includes an identifier of the first network slice.
[0326] In one possible implementation, the second information includes at least one of the following information: a first area identifier, a second area identifier, a network slice supported by the first TA, and a network slice supported by the second TA; wherein, the first area identifier is used to indicate the first TA, the second area identifier is used to indicate the second TA, when the host node of the first relay node is the first host node, the tracking area where the terminal device is located is the first TA, and the network slices supported by the first TA include the first network slice.
[0327] In a possible implementation, the first area identifier is a tracking area code TAC and / or a tracking area identifier TAI of a first TA, and the second area identifier is a TAC and / or TAI of a second TA.
[0328] In one possible implementation, the sending module 1102 is further used to: send third information to the terminal device, where the third information is used to indicate that the first network slice is supported by the first relay node.
[0329] In one possible implementation, the receiving module 1101 is used for the core network device to receive fourth information from the first host node, and the fourth information is used to indicate that the first host node has established a protocol data unit PDU session for the terminal device; the receiving module 1101 is also used to: receive fifth information from the first host node, and the fifth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node; the sending module 1102 is also used to: send sixth information to the second host node, and the sixth information is used to indicate that the second host node accepts the PDU session to be established indicated by the core network device, and the established PDU session includes the PDU session to be established.
[0330] In one possible implementation, the sending module 1102 is further used to: send a second allowed NSSAI to the second host node, where the second allowed NSSAI includes an identifier of the network slice associated with the PDU session to be established by the first host node.
[0331] In one possible implementation, the fifth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0332] In a second embodiment, the communication apparatus is applied to a terminal device.
[0333] Specifically, the sending module 1102 is used to send first information to the core network device, where the first information is used to request the service corresponding to the first network slice, and the terminal device accesses the first relay node; the receiving module is used to receive the first allowed network slice selection auxiliary information NSSAI from the core network device, where the first allowed NSSAI includes the identifier of the first network slice; wherein, the first network slice is not supported by the second tracking area TA, and when the host node of the first relay node is the second host node, the tracking area where the terminal device is located is the second TA.
[0334] In one possible implementation, the receiving module 1101 is further used to: receive third information from the core network device, where the third information is used to indicate that the first network slice is supported by the first relay node.
[0335] In one possible implementation, when the cell accessed by the terminal device changes from the first cell of the first relay node to the second cell, the sending module 1102 is also used to: initiate a tracking area update TAU; wherein, the first cell and the second cell of the first relay node are located in the same registration area RA, and the second cell does not belong to the first relay node.
[0336] In a possible implementation, the sending module 1102 specifically initiates a TAU when the system message broadcast by the second cell does not indicate that the second cell is the cell of the first relay node.
[0337] In a third embodiment, the communication device is applied to a second host node.
[0338] Specifically, the sending module 1102 is used to send second information to the core network device, where the second information is used to indicate that the first relay node supports the first network slice, and the first network slice is not supported by the second tracking area TA; the receiving module 1101 is used to receive the first allowed network slice selection auxiliary information NSSAI from the core network device, where the first allowed NSSAI includes the identifier of the first network slice; wherein, the service corresponding to the first network slice is the service requested by the terminal device to the core network device, and the terminal device accesses the first relay node, and the host node of the first relay node is the second host node. The tracking area where the terminal device is located is the second TA.
[0339] In one possible implementation, the second information includes at least one of the following information: a first area identifier, a second area identifier, a network slice supported by the first TA, and a network slice supported by the second TA; wherein, the first area identifier is used to indicate the first TA, the second area identifier is used to indicate the second TA, when the host node of the first relay node is the first host node, the tracking area where the terminal device is located is the first TA, and the network slices supported by the first TA include the first network slice.
[0340] In a possible implementation, the first area identifier is a tracking area code TAC and / or a tracking area identifier TAI of a first TA, and the second area identifier is a TAC and / or TAI of a second TA.
[0341] In one possible implementation, the communication device also includes a processing module 1103, and the receiving module 1101 is also used to: receive the sixth information from the core network device, the sixth information is used to indicate that the second host node accepts the protocol data unit PDU session to be established indicated by the core network device, and the PDU session established by the first host node for the terminal device includes the PDU session to be established; the processing module 1103 is used to: determine to receive the PDU session to be established.
[0342] In one possible implementation, the receiving module 1101 is further used to: receive a second allowed NSSAI from the core network device, where the second allowed NSSAI includes an identifier of a network slice associated with the PDU session to be established.
[0343] In a fourth embodiment, the communication device is applied to a first host node.
[0344] Specifically, the sending module 1102 is used to send fourth information to the core network device, and the fourth information is used to indicate that the first host node has established a protocol data unit PDU session for the terminal device; the sending module 1102 is also used to send fifth information to the core network device, and the fifth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node.
[0345] In one possible implementation, the fifth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0346] In a fifth embodiment, the communication device is applied to a second host node.
[0347] Specifically, the receiving module 1101 is used to receive the fourth information sent from the first host node, and the fourth information is used to indicate that the first host node has established a protocol data unit PDU session for the terminal device; the receiving module 1101 is also used to receive the fifth information from the first host node, and the fifth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node; the sending module 1102 is used to send the sixth information to the second host node, and the sixth information is used to indicate that the second host node accepts the PDU session to be established indicated by the core network device, and the established PDU session includes the PDU session to be established.
[0348] In one possible implementation, the sending module 1102 is further used to send a second allowed NSSAI to the second host node, where the second allowed NSSAI includes an identifier of a network slice associated with the PDU session established by the first host node for the terminal device.
[0349] In one possible implementation, the fifth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0350] In a sixth embodiment, the communication device is applied to a first host node.
[0351] Specifically, in the sixth embodiment, the sending module 1102 is used to send seventh information to the second host node, and the seventh information is used to request the second host node to accept the protocol data unit PDU session established by the first host node for the terminal device; the sending module 1102 is also used to send eighth information to the second host node, and the eighth information is used to indicate that the terminal device accesses the first relay node and is relatively stationary with respect to the first relay node.
[0352] Exemplarily, the eighth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0353] In the seventh embodiment, the communication device is applied to the second host node. In addition, in the seventh embodiment, the communication device further includes a processing module 1103 .
[0354] Specifically, in this sixth embodiment, the receiving module 1101 is used to receive the seventh information sent from the first host node, and the seventh information is used to request the second host node to accept the protocol data unit PDU session established by the first host node for the terminal device; the receiving module 1101 is also used to receive the eighth information from the first host node, and the eighth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node; the processing module 1103 is used to determine to accept the established PDU session.
[0355] In one possible implementation, the eighth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
[0356] In one possible implementation, the receiving module 1101 is also used to: receive third allowed network slice selection auxiliary information NSSAI from the core network device, where the third allowed NSSAI includes an identifier of the network slice associated with the established PDU session.
[0357] In an eighth embodiment, the communication device is applied to a first host node.
[0358] Specifically, in the eighth embodiment, the processing module 1103 is used to determine that the terminal device connected to the first relay node has established a protocol data unit PDU session, the host node of the first relay node is the first host node and the first relay node is deployed in the mobile device and moves with the mobile device; the sending module 1102 is used to send ninth information to the first relay node, and the ninth information is used to instruct the first relay node to prohibit updating the tracking area code TAC.
[0359] Optionally, the sending module 1102 sends the ninth information to the first relay node specifically when the network slice associated with the PDU session is not supported by the second TA.
[0360] In a possible implementation, the ninth information is further used to indicate a duration for prohibiting updating of the TAC in the first relay node.
[0361] Optionally, the ninth information includes a tracking area code TAC of a second TA, where the second TA is a tracking area where the terminal device is located when the host node of the first relay node is connected to the second host node.
[0362] In a ninth embodiment, the communication apparatus is applied to a terminal device.
[0363] Specifically, in the ninth embodiment, the sending module 1102 is used to prohibit sending the tracking area update TAU when the cell accessed by the terminal device changes from the second cell to the first cell of the first relay node; wherein the second cell does not belong to the first relay node, and can be a stationary cell on the ground. The first relay node is deployed in the mobile device and moves with the mobile device, and the terminal device is not stationary relative to the first relay node.
[0364] In a possible implementation, the sending module 1102 specifically prohibits sending TAU when receiving a system message broadcast by the first cell, where the system message broadcast by the first cell includes indication information indicating that the first cell is a cell of the first relay node and the TAC to which the first cell belongs.
[0365] In one possible implementation, the receiving module 1101 is used to: receive the tenth information sent by the core network device, the tenth information is used to indicate the tracking area code TAC list of the relay nodes near the terminal device and / or the cell list of the relay nodes near the terminal device; accordingly, the sending module 1102 is also used to: prohibit sending TAU when the TAC to the first cell or the cell identifier of the first cell is included in the content indicated by the tenth information.
[0366] In one possible implementation, the receiving module 1101 is used to: receive a registration area RA sent by a core network device, where the RA includes a TAC list of relay nodes near the terminal device and / or a cell list of relay nodes near the terminal device; accordingly, the sending module 1102 is also used to: prohibit sending TAU when it is determined that the TAC to which the first cell belongs or the cell identifier of the first cell is within the RA.
[0367] Figure 12 is a schematic structural diagram of a communication device provided in another embodiment of the present application. The device shown in Figure 12 can be used to execute the method described in any of the above embodiments.
[0368] As shown in Figure 12, the apparatus 1200 of this embodiment includes a memory 1201 and a processor 1202. Optionally, the apparatus 1200 further includes a communication interface 1203 and a bus 1204. The memory 1201, the processor 1202, and the communication interface 1203 are connected to each other via the bus 1204.
[0369] The memory 1201 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1201 may store a program. When the program stored in the memory 1201 is executed by the processor 1202, the processor 1202 is configured to perform the steps of the method shown in Figures 5 to 10.
[0370] The processor 1202 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits to execute relevant programs to implement the methods shown in Figures 5 to 10 of the present application.
[0371] The processor 1202 may also be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the method of Figures 5 to 10 of the embodiment of the present application may be completed by hardware integrated logic circuits in the processor 1202 or software instructions.
[0372] The processor 1202 may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor 1202 may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor.
[0373] The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 1201, and the processor 1202 reads the information in the memory 1201 and, in combination with its hardware, completes the functions required to be performed by the units included in the device of the present application. For example, the various steps / functions of the embodiments shown in Figures 5 to 10 can be executed.
[0374] The communication interface 1203 may use, but is not limited to, a transceiver or other transceiver device to implement communication between the apparatus 1200 and other devices or a communication network.
[0375] The bus 1204 may include a path for transmitting information between various components of the device 1200 (eg, the memory 1201 , the processor 1202 , and the communication interface 1203 ).
[0376] It should be understood that the apparatus 1200 shown in the embodiment of the present application can be an electronic device, or a chip configured in an electronic device. The apparatus 1200 can be deployed in a terminal device, or can also be deployed in a network device.
[0377] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can 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 program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.
[0378] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " as used herein generally indicates an "or" relationship between the associated objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.
[0379] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.
[0380] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0381] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0382] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0383] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0384] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0385] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0386] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, 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 and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.
[0387] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A communication method, It is characterized in that include: Receiving first information from a terminal device, where the first information is used to request a service corresponding to a first network slice, and the terminal device accesses a first relay node; receiving second information from a second host node, where the second information is used to indicate that the first relay node supports the first network slice, wherein the first network slice is not supported by a second tracking area TA, and when the host node of the first relay node is the second host node, the tracking area where the terminal device is located is the second TA; Sending first allowed network slice selection auxiliary information NSSAI to the terminal device and / or the second host node, wherein the first allowed NSSAI includes an identifier of the first network slice.
2. The method according to claim 1, It is characterized in that The second information includes at least one of the following information: a first area identifier, a second area identifier, a network slice supported by the first TA, and a network slice supported by the second TA; Among them, the first area identifier is used to indicate the first TA, the second area identifier is used to indicate the second TA, when the host node of the first relay node is the first host node, the tracking area where the terminal device is located is the first TA, and the network slices supported by the first TA include the first network slice.
3. The method according to claim 2, It is characterized in that The first area identifier is a tracking area code TAC and / or a tracking area identifier TAI of the first TA, and the second area identifier is a TAC and / or TAI of the second TA.
4. The method according to any one of claims 1 to 3, It is characterized in that The method further comprises: Send third information to the terminal device, where the third information is used to indicate that the first network slice is supported by the first relay node.
5. The method according to any one of claims 2 to 4, It is characterized in that The method further comprises: receiving fourth information from the first host node, where the fourth information is used to indicate a protocol data unit (PDU) session that the first host node has established for the terminal device; receiving fifth information from the first host node, where the fifth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node; Sending sixth information to the second host node, where the sixth information is used to instruct the second host node to accept the PDU session to be established indicated by the core network device; The established PDU session includes the PDU session to be established.
6. The method according to claim 5, It is characterized in that The method further comprises: A second allowed NSSAI is sent to the second host node, wherein the second allowed NSSAI includes an identifier of the network slice associated with the PDU session to be established.
7. The method according to claim 5 or 6, It is characterized in that The fifth information is in any one of the following two forms: indicating that the reason for the switching request is the distributed unit DU migration or the mobile terminal MT migration of the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
8. A communication method, It is characterized in that include: Sending first information to a core network device, where the first information is used by a terminal device to request a service corresponding to a first network slice, and the terminal device accesses a first relay node; Receiving first allowed network slice selection assistance information NSSAI from the core network device, where the first allowed NSSAI includes an identifier of the first network slice; Among them, the first network slice is not supported by the second tracking area TA, and when the host node of the first relay node is the second host node, the tracking area where the terminal device is located is the second TA.
9. The method according to claim 8, It is characterized in that The method further comprises: Receive third information from the core network device, where the third information is used to indicate that the first network slice is supported by the first relay node.
10. The method according to claim 9, It is characterized in that When the cell accessed by the terminal device changes from the first cell of the first relay node to the second cell, the method further includes: Initiate tracking area update TAU; The first cell of the first relay node and the second cell are located in the same registration area RA, and the second cell does not belong to the first relay node.
11. The method according to claim 10, It is characterized in that The initiating tracking area update TAU includes: When the system message broadcast by the second cell does not indicate that the second cell is a cell of the first relay node, a TAU is initiated.
12. A communication method, It is characterized in that include: Sending seventh information to the second host node, wherein the seventh information is used to request the second host node to accept the protocol data unit PDU session established by the first host node for the terminal device, and the seventh information includes a session identifier associated with the established PDU session and an identifier of the network slice; Sending eighth information to the second host node, where the eighth information is used to indicate that the terminal device is connected to the first relay node and is relatively stationary with respect to the first relay node.
13. The method according to claim 12, It is characterized in that The eighth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
14. A communication method, It is characterized in that The method comprises: Receive seventh information sent from the first host node, where the seventh information is used to request the second host node to accept the protocol data unit PDU session established by the first host node for the terminal device, and the seventh information includes a session identifier associated with the established PDU session and an identifier of the network slice; receiving eighth information from the first host node, where the eighth information is used to indicate that the terminal device is connected to a first relay node and is relatively stationary with respect to the first relay node; Determine to accept the established PDU session.
15. The method according to claim 14, It is characterized in that The eighth information is in any one of the following two forms: indicating that the reason for the switching request is the migration of the distributed unit DU or the migration of the mobile terminal MT in the first relay node, and when the host node of the first relay node is the first host node, the cell where the terminal device is located is the cell of the first relay node.
16. The method according to claim 14 or 15, It is characterized in that The method further comprises: Receive third allowed network slice selection auxiliary information NSSAI from the core network device, wherein the third allowed NSSAI includes an identifier of the network slice associated with the established PDU session.
17. A communication device, It is characterized in that include: a processor coupled to the memory; The memory is used to store program instructions; The processor is used to call the program instructions in the memory to execute the method according to any one of claims 1 to 7 or 8 to 11 or 12 to 13 or 14 to 16.
18. A computer readable medium, It is characterized in that The computer-readable medium stores a program code for computer execution, the program code comprising instructions for executing the method according to any one of claims 1 to 7 or claims 8 to 11 or claims 12 to 13 or claims 14 to 16.
19. A computer program product, It is characterized in that The computer program product includes computer program codes, and when the computer program codes are run on a computer, the computer is enabled to implement the method according to any one of claims 1 to 7, claims 8 to 11, claims 12 to 13, or claims 14 to 16.
Citation Information
Patent Citations
Communication method and communication device
CN118921703A
Improving service continuity
EP4122241A1
Mobility enhancement with network slicing
US20210037455A1
Re-mapping network slices for supporting service continuity
US20220330117A1
WTRU-to-network relay
US20230023639A1
