Communication methods and devices, storage media and chip systems

Abstract

A communication method and device, a storage medium, and a chip system are disclosed, which are configured to implement a URSP function by using a communication processor attached to the communication device to improve the usage of the URSP function in a product. In this application, a wireless communication device includes a communication processor and an application processor, and the communication processor is coupled to the application processor. The communication processor is configured to receive a first request sent by the application processor, the first request being used to query a routing descriptor. The first request includes a path information parameter corresponding to data to be transmitted. The communication processor is configured to send a second request to a network device. The second request is used to activate a PDU session. The second request includes at least one parameter in the routing descriptor. The routing descriptor matches the path information parameter. The URSP function is implemented by using the attached communication processor. In this way, the usage of the URSP function in a product can be improved.

Description

Technical Field

[0001]

[0001] This application relates to the field of communication technologies, and in particular, to communication methods and devices, storage media, and chip systems.

Background Art

[0002]

[0002] The 3rd Generation Partnership Project (3GPP) defines a User Equipment Route Selection Policy (URSP). The URSP is used to determine Route Selection Descriptors (RSDs) required by various applications (APPs) and data packets, such as network slices (NS), Data Network Names (DNN), and session and service continuity (SSC) modes. The terminal device can use the URSP to determine the corresponding RSD based on the network requirements of the APP, establish a protocol data unit (PDU) session based on the determined RSD, and then transmit the data of the APP by using the established PDU session.

[0003]

[0003] Currently, no protocol specifies the usage of URSP. Only the 3GPP 27.007 protocol defines two related AT commands. The modem reports information containing URSP and information distributed by the network, such as user policy information (UE policy section), to the upper layer system in the form of an original code stream by using the +CRUEPOLICY command (the upper layer system usually refers to the operating system or application control layer). The upper layer system decodes the original code stream and returns the decoded original code stream to the modem by using the +CSUEPOLICY command. The modem then forwards the decoded original code stream to the network.

[0004]

[0004] According to the 3GPP 27.007 protocol, URSP-related operations tend to be performed in higher-layer systems. However, for some communication device manufacturers, such as mobile phone manufacturers, the operating system used by the manufacturer, such as Android, is controlled by the system publisher, making it difficult to modify the control layer code for certain types of functions. If URSP functionality is required to be used in the communication device, each manufacturer needs to develop and maintain the URSP functionality themselves, and the protocol parsing code in the operating system needs to be modified in sync with 3GPP protocol upgrades. Consequently, development and maintenance costs are high. Based on this, each manufacturer does not want to implement URSP in their communication devices. For some small communication device manufacturers, such as non-mobile phone manufacturers, many of their products do not have an operating system, only an application control layer, and basically do not have the ability to parse the 3GPP protocol and fully implement URSP functionality according to the protocol, and it is even more difficult to upgrade them in conjunction with 3GPP protocol upgrades. Consequently, URSP functionality cannot currently be implemented in such communication devices.

[0005]

[0005] Based on this, the urgent issue that needs to be resolved is how to improve the usage of the URSP function in the product. [Overview of the project]

[0006]

[0006] This application provides a communication method and apparatus, a storage medium, and a chip system for performing URSP functions by using a communication processor attached to a communication device.

[0007]

[0007] In the solutions provided in the embodiments of this application, the communication device may be a wireless communication device, or it may be some component within a wireless communication device, such as an integrated circuit product like a system chip or a communication chip. The wireless communication device may also be a computer device that supports wireless communication functions.

[0008]

[0008] Specifically, the wireless communication device may be a terminal such as a smartphone, or a wireless access network device such as a base station. The system chip may also be called a system on a chip (SoC), or simply an SoC chip. The communication chip may include a baseband processing chip and a radio frequency processing chip. The baseband processing chip is sometimes also called a modem or baseband chip. The radio frequency processing chip is sometimes also called a radio frequency transceiver or radio frequency chip. In physical implementation, some or all of the communication chips may be integrated into the SoC chip. For example, the baseband processing chip may be integrated into the SoC chip, but the radio frequency processing chip may not be integrated into the SoC chip.

[0009]

[0009] According to a first embodiment, a wireless communication device is provided which includes a communication processor. The communication processor includes a processing circuit and an interface circuit coupled to the processing circuit. The processing circuit is configured to receive a first request transmitted by an application processor via the interface circuit; and to transmit a second request to a network device via the interface circuit. The first request is used to query a route selection descriptor. The first request includes route information parameters corresponding to the data to be transmitted. The second request is used to activate a session. The second request includes at least one parameter in the route selection descriptor. The route selection descriptor matches the route information parameter. The communication processor can know that, based on the first request, it is possible to trigger an operation to query a route selection descriptor, and then, based on the found route selection descriptor that matches the route information parameter, to request the establishment of a session from the network device. In this way, the URSP function is performed on the wireless communication device. Furthermore, this solution does not require other vendors to develop and maintain URSP functionality at the operating system layer, thereby reducing vendor costs. Moreover, in the case of wireless communication devices that do not have an operating system, or whose operating system does not have the capability to perform decoding based on the original code stream corresponding to the URSP rules, the URSP functionality can be implemented alternatively by using the installed communication processor. In this way, it is possible to improve the use of URSP functionality in products.

[0010]

[0010] In possible implementations, the routing information parameters are the same as the parameters included in the traffic descriptors within the target URSP rule. The route selection descriptor is the route selection descriptor within the target URSP rule. The routing information parameters are matched against the traffic descriptors within the target URSP rule to discover the target URSP rule, and then the route selection descriptor that matches the routing information parameters is retrieved. In this way, the routing information parameters may be more compatible with the URSP functionality in the standard.

[0011]

[0011] In possible implementations, the routing information parameters include at least one of the following parameters: destination address parameter for the data to be transmitted; data network parameter corresponding to the data to be transmitted; application descriptor corresponding to the data to be transmitted; or connection capability parameter corresponding to the data to be transmitted. The route selection descriptor can be queried based on multiple types of parameters, thereby improving the flexibility of the solution.

[0012]

[0012] In possible implementations, a traffic descriptor includes at least one of the following parameters: destination address parameter; data network parameter; application descriptor; or connection capability parameter. The parameter type of the traffic descriptor is essentially the same as the parameter type of the routing information parameter. Thus, the requested route selection descriptor is found by matching the two parameters.

[0013]

[0013] In possible implementations, the destination address parameter includes at least one of the following parameters: a domain descriptor corresponding to the data to be transmitted; an Internet Protocol IP descriptor corresponding to the data to be transmitted; or a non-IP descriptor corresponding to the data to be transmitted. The existence of multiple types of destination address parameters makes it possible to improve the flexibility of the solution.

[0014]

[0014] In possible implementations, the data network parameters include a DNN. Thus, the data network required by the data to be transmitted can be determined based on the DNN.

[0015]

[0015] In possible implementations, the parameters in the route selection descriptor include parameters that the session requires to be matched. The parameters that the session requires to be matched include at least one of the following: network parameters requested by the session; network slice parameters requested by the session; or session service parameters requested by the session. Since there are a large number of parameter types in the route selection descriptor, session creation requirements can be met from multiple perspectives, making it possible to provide users with more personalized services.

[0016]

[0016] In possible implementations, the network parameters include at least one of the following parameters: session type; data network name DNN; access type priority; or non-seamless offload instruction. Since there are a large number of network parameter types, it is possible to improve the flexibility of the solution and provide users with more personalized services.

[0017]

[0017] In possible implementations, the network slice parameters include at least one of the following parameters: network slice type or network slice name. Thus, the network slice parameters requested by a session can be determined based on the network slice type or name.

[0018]

[0018] In possible implementations, session service parameters include session and service continuity SSC parameters. Session-based service parameters can provide users with a service mode suitable for the session characteristics.

[0019]

[0019] In possible implementations, the first request is further used to activate the session. Thus, the first request may include two functions: matching the route selection descriptor and activating the session. The communications processor can then perform two actions based on the first request: querying the route selection descriptor and activating the session. It can be seen that this solution requires little change to the application processor and only requires that the first request be sent. The URSP functionality is implemented by the communications processor, which can reduce the workload of various vendors modifying the operating system.

[0020]

[0020] In possible implementations, the first request includes at least one of the following: +CACT;+CPSDIAL;+CACT;+CEST; or +CCONN. In this way, the functionality of the first request can be implemented in a manner that is more compatible with prior art by using newly defined AT commands. Furthermore, the "ACT" in this command includes the meaning of activating the session, making it more practical and easier for the user to understand the meaning of this command.

[0021]

[0021] In possible implementations, the processing circuit is further configured, after receiving a first request sent by the application processor and before sending a second request to the network device, to return a first response to the application processor via the interface circuit, where the first response includes at least one parameter in the route selection descriptor. In this way, the communication processor can return at least one parameter in the discovered route selection descriptor to the application processor, which in turn can use that parameter as a dialing parameter when activating a session, thereby performing the URSP function.

[0022]

[0022] In possible implementations, the first request includes at least one of the following: +C5GRSDQRY;+C5GURSPQRY;+CURSPQRY;+CQRSD;+C5GQRSD; or +C5GRURSP. In this way, the query function of the first request can be implemented in a manner that is more compatible with prior art by using newly defined AT commands. Furthermore, “5GRSDQRY” in this command is used by including “5GRSDQRY” in the 5G network, and its function is to query the route selection descriptor, which is more practical and easier for the user to understand.

[0023]

[0023] In possible implementations, the first response further includes the priority of the route selection descriptors. In this way, the application processor can sequentially select and dial based on the priority of various route selection descriptors in order to create a session.

[0024]

[0024] In a possible implementation, after returning the first response and before sending the second request to the network device, the communication processor is further configured to receive a third request sent by the application processor, where the third request is used to activate a session and includes at least one parameter in a route selection descriptor. In this implementation, the third request can carry the route selection descriptor queried from the communication processor. Thus, the route selection descriptor can be selected by the application processor. Furthermore, the solution is made to implement URSP functionality, which improves the versatility of this embodiment of the present application and makes it possible to provide users with more alternative implementation solutions, thereby improving flexibility.

[0025]

[0025] In possible implementations, the second request is a session establishment request. The second request sent by the communication processor may be a session establishment request as defined in an existing protocol. 5G technology is used as an example. The second request may also be a PDU session establishment request, which carries at least one parameter in the route selection descriptor as a dialing parameter. In this way, the route selection descriptor may be more compatible with existing protocols.

[0026]

[0026] In possible implementations, the processing circuit is further configured to receive by the interface circuit at least one URSP rule delivered by a network device, corresponding to a wireless communication device, where the URSP rule in at least one URSP rule includes a traffic descriptor and at least one route selection descriptor; and the processing circuit is configured by the interface circuit to send a first message to an application processor, where the first message includes parameters of at least one traffic descriptor in at least one URSP rule. In this way, decoding of the original code stream of the URSP rule can be offloaded to the communication processor for implementation, thereby reducing the requirements of the application processor. Furthermore, sending the traffic descriptor to the application processor may provide the application processor with a basis for performing preliminary filtering.

[0027]

[0027] In possible implementations, the first message includes at least one of the following: +C5GTDRPT; +CTDRPT; +CURSPRPT; or +C5GTD. In this way, the query function for the first request can be implemented in a manner that is more compatible with prior art by using newly defined AT commands. The command can also include the meaning of returning a traffic descriptor, which makes it more practical and easier for the user to understand the meaning of the command.

[0028]

[0028] In a possible implementation, the wireless communication device further includes an application processor, and the communication processor is coupled to the application processor. Specifically, the application processor is configured to determine whether a traffic descriptor that meets a pre-set condition exists in at least one received traffic descriptor, and the pre-set condition includes that the parameters of the traffic descriptor match the path information parameters. When a traffic descriptor that meets the pre-set condition exists, a first request is sent. In this way, since the application processor can perform preliminary screening, the application processor may send the first request after determining that a traffic descriptor corresponding to the path information parameters exists in the URSP rules distributed by the network. In another possible implementation, if it is found that a traffic descriptor that matches the path information parameters does not exist in the URSP rules distributed by the network, the original solution may be used. Specifically, after receiving a PDU session activation request, the communication processor directly starts a PDU session with the network without querying the routing descriptor. However, the parameters of the routing descriptor are no longer used as the dialing parameters in the PDU session. In yet another possible implementation, if a traffic descriptor that matches the path information parameters does not exist in the URSP rules distributed by the network, it may be determined that the session has not been successfully activated.

[0029]

[0029] In a possible implementation, further, after the processing circuit transmits the second request to the network device, the interface circuit is configured to receive a second response, where the second response indicates that the session has been successfully activated; the processing circuit is configured to return a third response to the application processor, where the third response indicates that the session has been successfully activated. After receiving a message indicating that the session has been successfully activated, the communication processor may indicate to the application processor that the session has been successfully activated and transmit a session message, as a result of which the application processor transmits data based on the activated session.

[0030]

[0030] In another possible implementation, the processing circuit further: when a message indicating that the session has not been successfully activated is received by the interface circuit, the communication processor is configured to automatically select a route selection descriptor with a second priority and continue to initiate the session activation procedure until the session is successfully activated or all matching route selection descriptors are exhausted. Thus, the communication processor may choose to feedback to the application processor a message indicating that the session has not been successfully activated, or may not feedback a message indicating that the session has not been successfully activated.

[0031]

[0031] In yet another possible implementation, the processing circuit is further configured by the interface circuit to return a message to the application processor indicating that the session has not been successfully activated, and as a result, the application processor continues to select a route selection descriptor with second priority and initiate the session activation procedure until the session is successfully activated or until all matching route selection descriptors are exhausted.

[0032]

[0032] In a possible implementation, the processing circuit is configured to receive, by interface circuit, an original code stream corresponding to at least one URSP rule corresponding to a wireless communication device, which is delivered by a network device; to decode the original code stream corresponding to the URSP rule in order to obtain at least one URSP rule; and to store at least one URSP rule in memory. In this way, the decoding of the original code stream of the URSP rule can be offloaded to the communication processor for implementation, thereby reducing the requirements of the application processor.

[0033]

[0033] In possible implementations, the application processor is not capable of performing decoding based on the original code stream corresponding to the URSP rule. Thus, the decoding of the original code stream of the URSP rule can be offloaded to the communications processor for implementation, thereby reducing the requirements of the application processor. This provides a basis for the application processor to popularize URSP functionality in wireless communications devices with limited capabilities.

[0034]

[0034] According to a second aspect, an embodiment of the present application provides a communication method applicable to a wireless communication device including a communication processor. The method includes: receiving a first request transmitted by an application processor with the communication processor; and transmitting a second request by the communication processor to a network device. The first request is used to query a route selection descriptor, and the first request includes route information parameters corresponding to the data to be transmitted. The second request is used to activate a session, and the second request includes at least one parameter in the route selection descriptor, which matches the route information parameter. The communication processor can know that, based on the first request, it is possible to trigger an operation to query a route selection descriptor, and then, based on the found route selection descriptor that matches the route information parameter, to request the establishment of a session from the network. In this way, the URSP function is performed on the wireless communication device. Furthermore, this solution does not require other vendors to develop and maintain URSP functionality at the operating system layer, thereby reducing vendor costs. Additionally, in the case of wireless communication devices without an operating system, or wireless communication devices whose operating system lacks the ability to perform decoding based on the original code stream corresponding to the URSP rules, the URSP functionality can be implemented alternatively by using the installed communication processor. In this way, it is possible to improve the use of URSP functionality in products.

[0035]

[0035] In possible implementations, the routing information parameters are the same as the parameters included in the traffic descriptors within the target URSP rule. The route selection descriptor is the route selection descriptor within the target URSP rule. The routing information parameters are matched against the traffic descriptors within the URSP rule to discover the target URSP rule, and then the route selection descriptor that matches the routing information parameters is retrieved. In this way, the routing information parameters may be more compatible with the URSP functionality in the standard.

[0036]

[0036] In possible implementations, the routing information parameters include at least one of the following parameters: destination address parameter for the data to be transmitted; data network parameter corresponding to the data to be transmitted; application descriptor corresponding to the data to be transmitted; or connection capability parameter corresponding to the data to be transmitted. The route selection descriptor can be queried based on multiple types of parameters, thereby improving the flexibility of the solution.

[0037]

[0037] In possible implementations, a traffic descriptor includes at least one of the following parameters: destination address parameter; data network parameter; application descriptor; or connection capability parameter. The parameter type of the traffic descriptor is essentially the same as the parameter type of the routing information parameter. Thus, the requested route selection descriptor is found by matching the two parameters.

[0038]

[0038] In possible implementations, the destination address parameter includes at least one of the following parameters: a domain descriptor corresponding to the data to be transmitted; an Internet Protocol IP descriptor corresponding to the data to be transmitted; or a non-IP descriptor corresponding to the data to be transmitted. The existence of multiple types of destination address parameters makes it possible to improve the flexibility of the solution.

[0039]

[0039] In possible implementations, the data network parameters include a DNN. Thus, the data network required by the data to be transmitted can be determined based on the DNN.

[0040]

[0040] In possible implementations, the parameters in the route selection descriptor include parameters that the session requires to be matched. The parameters that the session requires to be matched include at least one of the following: network parameters requested by the session; network slice parameters requested by the session; or session service parameters requested by the session. Since there are a large number of parameter types in the route selection descriptor, session creation requirements can be met from multiple perspectives, making it possible to provide users with more personalized services.

[0041]

[0044] In possible implementations, network parameters include at least one of the following parameters: session type; data network name DNN; access type priority; or non-seamless offload instruction. The large number of network parameter types allows for improved solution flexibility and enables the provision of more personalized services to users.

[0042]

[0042] In possible implementations, the network slice parameters include at least one of the following parameters: network slice type or network slice name. Thus, the network slice parameters requested by a session can be determined based on the network slice type or name.

[0043]

[0043] In possible implementations, session service parameters include session and service continuity SSC parameters. Session-based service parameters can provide users with a service mode suitable for the session characteristics.

[0044]

[0044] In possible implementations, the first request is further used to activate the session. Thus, the first request may include two functions: matching the route selection descriptor and activating the session. The communications processor can then perform two actions based on the first request: querying the route selection descriptor and activating the session. It can be seen that this solution requires little change to the application processor and only requires that the first request be sent. The URSP functionality is implemented by the communications processor, which can reduce the workload of various vendors modifying the operating system.

[0045]

[0045] In a possible implementation, after receiving a first request sent by the application processor and before sending a second request to the network device, the communication processor further returns a first response to the application processor, the first response including at least one parameter in the route selection descriptor. In this way, the communication processor can return at least one parameter in the discovered route selection descriptor to the application processor, as a result the application processor uses that parameter as a dialing parameter when activating a session, thereby performing the URSP function.

[0046]

[0046] In possible implementations, the first response further includes the priority of the route selection descriptors. In this way, the application processor can sequentially select and dial based on the priority of various route selection descriptors in order to create a session.

[0047]

[0047] In a possible implementation, after the communication processor has returned a first response and before sending a second request to a network device, the method further includes the step of: receiving a third request sent by the application processor, the communication processor having received the third request which is used to activate a session and which includes at least one parameter in a route selection descriptor. In this implementation, the third request may carry a route selection descriptor queried from the communication processor. Thus, the route selection descriptor may be selected by the application processor. Furthermore, the solution is made to implement URSP functionality, which improves the versatility of this embodiment of the present application and makes it possible to provide users with more alternative implementation solutions, thereby improving flexibility.

[0048]

[0048] In a possible implementation, the second request is a session establishment request, and the second request includes at least one parameter in the route selection descriptor. The second request transmitted by the communication processor may be a session establishment request as defined in an existing protocol. 5G technology is used as an example. The second request may also be a PDU session establishment request, and carries at least one parameter in the route selection descriptor as a dialing parameter. In this way, the route selection descriptor may be more compatible with existing protocols.

[0049]

[0049] In a possible implementation, prior to the step of receiving a first request sent by the application processor by the communication processor, the method further includes: a step of receiving by the communication processor at least one URSP rule delivered by a network device, which corresponds to a wireless communication device, wherein the URSP rule in at least one URSP rule includes a traffic descriptor and at least one route selection descriptor; and a step of sending a first message by the communication processor to the application processor, wherein the first message includes parameters of at least one traffic descriptor in at least one URSP rule. In this way, decoding of the original code stream of the URSP rule can be offloaded to the communication processor for implementation, thereby reducing the requirements of the application processor. Furthermore, sending the traffic descriptor to the application processor may provide the application processor with a basis for performing preliminary filtering.

[0050]

[0050] In a possible implementation, after sending a first message to the application processor, the method further includes: the application processor determining whether a traffic descriptor that matches a pre-configured condition exists in at least one of the received traffic descriptors, wherein the pre-configured condition includes: the parameters of the traffic descriptor match the routing information parameters; and, if a traffic descriptor that matches the pre-configured condition exists, the method sending a first request. Thus, the application processor can perform a preliminary screening, so that the application processor may send a first request after determining that a traffic descriptor corresponding to the routing information parameters exists in a URSP rule delivered by the network. In another possible implementation, if it is found that a traffic descriptor matching the routing information parameters does not exist within the URSP rules delivered by the network, the original solution may be used. Specifically, after receiving a session activation request, the communications processor directly initiates a session to the network without querying a route selection descriptor. However, the parameters of the route selection descriptor are no longer used as dialing parameters in the session. In yet another possible implementation, if a traffic descriptor matching the routing information parameters is not present in the URSP rules distributed by the network, the session may be determined to have not been successfully activated.

[0051]

[0051] In a possible implementation, after the communication processor sends a second request to the network device, the communication processor further receives a second response and returns a third response to the application processor. The second response indicates that the session has been successfully activated. The third response indicates that the session has been successfully activated. After receiving a message indicating that the session has been successfully activated, the communication processor may indicate to the application processor that the session has been successfully activated and send a session message, which in turn causes the application processor to send data based on the activated session.

[0052]

[0052] In another possible implementation, if a message is received indicating that the session has not been successfully activated, the communication processor may continue to initiate the session activation procedure itself by selecting a route selection descriptor with second priority until the session is successfully activated or until all matching route selection descriptors have been exhausted. Thus, the communication processor may choose to feed back the message indicating that the session has not been successfully activated to the application processor, or it may choose not to.

[0053]

[0053] In yet another possible implementation, the communications processor may return a message to the application processor indicating that the session has not been successfully activated, and the application processor may continue to initiate the session activation procedure by selecting the second-highest priority route selection descriptor until the session is successfully activated or until all matching route selection descriptors have been exhausted.

[0054]

[0054] In a possible implementation, before the communication processor receives the first request sent by the application processor, the communication processor receives, by the communication processor, an original code stream corresponding to at least one URSP rule corresponding to a wireless communication device, which is delivered by the network device; decodes the original code stream corresponding to the URSP rule in order to obtain at least one URSP rule; and stores at least one URSP rule in memory. In this way, the decoding of the original code stream of the URSP rule can be offloaded to the communication processor for implementation, thereby reducing the requirements of the application processor.

[0055]

[0055] In possible implementations, the application processor is not capable of performing decoding based on the original code stream corresponding to the URSP rule. Thus, the decoding of the original code stream of the URSP rule can be offloaded to the communications processor for implementation, thereby reducing the requirements of the application processor. This provides a basis for the application processor to popularize URSP functionality in wireless communications devices with limited capabilities.

[0056]

[0056] The present application further provides a communication device including a processor and memory. The memory is configured to store program instructions. The processor is configured to execute program instructions stored in the memory to perform any possible method in a second embodiment.

[0057]

[0057] The present application further provides a communication device including a processor and an interface circuit. The interface circuit is configured to access a memory, which stores program instructions. The processor is configured to access the memory via the interface circuit and execute the program instructions stored in the memory to perform any possible method in the second embodiment.

[0058]

[0058] The present application provides a computer-readable storage medium that stores computer-readable instructions. When a computer reads and executes a computer-readable instruction, the computer can perform any of the methods described above for possible designs.

[0059]

[0059] The present application provides a computer program product. When a computer loads and runs the computer program product, the computer becomes capable of performing any method of any of the possible designs described above.

[0060]

[0060] The present application provides a chip which is connected to memory and configured to read and execute software programs stored in memory and to carry out any of the methods in any of the possible designs described above. [Brief explanation of the drawing]

[0061] [Figure 1]

[0061] Figure 1 is a schematic diagram of the architecture of a communication system to which the embodiment of the present application can be applied. [Figure 2a]

[0062] Figure 2a is a schematic diagram of the structure of a wireless communication device according to an embodiment of the present application. [Figure 2b]

[0063] Figure 2b is a schematic diagram of the structure of a wireless communication device according to an embodiment of the present application. [Figure 3]

[0064] Figure 3 is a schematic diagram of the structure of a wireless communication device according to an embodiment of the present application. [Figure 4A]

[0065] Figures 4A and 4B are schematic flowcharts of possible communication methods according to the embodiments of this application. [Figure 4B]

[0065] Figures 4A and 4B are schematic flowcharts of possible communication methods according to the embodiments of the present application. [Figure 5A]

[0066] Figures 5A and 5B are schematic flowcharts of another possible communication method according to the embodiment of the present application. [Figure 5B]

[0066] Figures 5A and 5B are schematic flowcharts of another possible communication method according to an embodiment of the present application. [Modes for carrying out the invention]

[0062]

[0067] The embodiments of this application will be described below with reference to the attached drawings.

[0063]

[0068] The technical solutions in the embodiments of this application may be applicable to various communication systems, such as Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, 5th Generation (5G) systems, New Radio (NR), and future 6th Generation (6G) systems, but are not limited to these.

[0064]

[0069] Figure 1 is a schematic diagram of the architecture of an example of a communication system to which the embodiments of the present application can be applied. As shown in Figure 1, the communication system includes terminal devices 10 and network devices. Network devices are typically owned by a carrier or infrastructure provider and operated or maintained by these vendors. Network devices may be further divided into radio access network (R)AN devices 20 and core network (CN) devices 30. RAN devices include base stations (BS), small cells, 5G routers, etc.

[0065]

[0070] In the solutions provided in the embodiments of this application, it should be understood that the wireless communication device may be a wireless communication device, or it may be some component within a wireless communication device, such as an integrated circuit product like a system chip or a communication chip. The wireless communication device may also be a computer device that supports wireless communication functions.

[0066]

[0071] Specifically, the wireless communication device may be a terminal device 10 (e.g., a smartphone) or an (R)AN device 20 (e.g., an (R)AN device such as a base station). The system chip may also be referred to as a system on a chip (SoC), or simply as an SoC chip. The communication chip may include a baseband processing chip and a radio frequency processing chip. The baseband processing chip is sometimes referred to as a modem or baseband chip. The radio frequency processing chip is sometimes referred to as a radio frequency transceiver or radio frequency chip. In physical implementation, some or all of the communication chip may be integrated into the SoC chip. For example, the baseband processing chip may be integrated into the SoC chip, but the radio frequency processing chip may not.

[0067]

[0072] The following describes the device related to the embodiment of this application with reference to Figure 1.

[0068]

[0073] (1) Terminal device 10

[0074] Terminal device 10 may also be referred to as a terminal. A terminal is capable of establishing a connection to a network device and providing a specific wireless communication service to a user based on the services of the network device. It should be understood that, because terminals have a closer relationship with the user, terminals are often also referred to as user equipment (UE) or subscriber unit (SU). Furthermore, compared to base stations, which are usually located in a fixed position, terminals usually move with the user and are sometimes referred to as mobile stations (MS). In addition, some network devices, such as relay nodes (RN) or wireless routers, may also sometimes be considered terminals because the network device has a UE identifier or belongs to a user.

[0069]

[0075] Specifically, terminals may include mobile phones, tablet computers, laptop computers, wearable devices (e.g., smartwatches, smart bands, smart helmets, or smart glasses), other devices with wireless access capabilities, such as intelligent vehicles, various Internet of Things (IoT) devices, and various smart home devices (e.g., smart meters and smart appliances) and smart city devices (e.g., security or surveillance devices and intelligent road traffic equipment).

[0070]

[0076] (2)(R)AN device 20

[0077] It should be understood that the (R)AN device 20 is configured to provide network access functionality to authorized terminal devices within a specific area, and that it can use transmission tunnels of different qualities based on the level of the terminal devices, service requirements, etc. The (R)AN device 20 is capable of managing radio resources, providing access services to terminal devices, and further completing the transfer of control signals and terminal device data between terminal devices and the core network. Access network devices may include various forms of base stations such as macro base stations, micro base stations (also referred to as small cells), relay stations, and access points.

[0071]

[0078] Furthermore, base stations may occasionally be referred to as wireless access points (APs) or transmission reception points (TRPs). Specifically, a base station may be a generation Node B (gNB) in a 5G new radio (NR) system, or an evolved Node B (eNB) in a 4G long-term evolution (LTE) system. Base stations may be classified as macro base stations or micro base stations based on their various physical forms or transmission power. Micro base stations are also sometimes referred to as small base stations or small cells.

[0072]

[0079] The (R)AN device 20 may differ specifically depending on the communication system.

[0073]

[0080] For example, a 5G access network device could be a next-generation Node B (gNB). A gNB could be connected to a terminal device, and the gNB and the terminal device communicate with each other using new radio (NR) access technology. That is, the gNB communicates with the terminal device via an NR link.

[0074]

[0081] The 4G access network device may be an evolved Node B (eNB). The terminal device may be located within the signal coverage area of ​​the 4G access network device. The terminal device may be connected to the 4G access network device and communicate with the 4G access network device via an LTE link.

[0075]

[0082] A 2G access network device may be a base transceiver station (BTS) or a base station controller (BSC). A 3G access network device may be a node B, or it may be referred to as a base station or radio network controller (RNC).

[0076]

[0083] (3) Core network (CN) device 30

[0084] Core network devices are configured to provide user connections and perform user management and service delivery. For example, establishing user connections includes functions such as mobile management (MM) and paging. User management includes user description, QoS, and security (corresponding security measures provided by the authentication center include security management of mobile services and security processing in external network access). Bearer connections include externally connected public switched telephone networks (PSTN), external line data networks, external packet data networks, and the Internet.

[0077]

[0085] In different communication systems, the core network device 30 may differ in specific ways.

[0078]

[0086] For example, the core network devices within a 5G communication system may also be referred to as the 5G core network (5GC). Network elements in the 5GC are functional virtual units and may include, but are not limited to, units used for access and mobility management functions (AMF), units used for session management functions (SMF), and network elements used for unified data management (UDM).

[0079]

[0087] Furthermore, the core network devices in a 4G communication system may also be referred to as the evolved packet core (EPC). The EPC primarily includes the following network elements: mobility management entity (MME), serving gateway (SGW), packet data network gateway (PGW), home subscriber server (HSS), and application server. The main functions of the MME include access control, mobility management, attaching and detaching, and session management (e.g., bearer establishment, modification, and release). The SGW is primarily configured to route and forward data packets. The main functions of the PGW include user-based packet filtering, lawful interception, and IP address assignment. The HSS is configured to store user subscription information, user subscription data, mobile user location information, etc.

[0080]

[0088] 2G / 3G core network devices may include mobile switching centers (MSCs) and base station controllers (BSCs).

[0081]

[0089] Figure 2a is an example of a schematic diagram of the structure of a wireless communication device according to an embodiment of the present application.

[0082]

[0090] As shown in Figure 2a, the wireless communication device may include a processor 100. In this embodiment of the present application, the processor 100 may include an application processor 110 and a communication processor 1501. The communication processor 1501 may be a modem 15011. The wireless communication device may further include a communication interface 120, memory 130, antenna 1, antenna 2 (antennas 1 and 2 are used as examples in Figure 2a, and additional antennas may be optionally included), a mobile communication module 150, a wireless communication module 140, and the like. The communication processor 1501 may be located within the mobile communication module 150 or in a different location. For example, the communication processor 1501 and the application processor 110 may be located on the same chip. In the drawings, an example is used in which the communication processor 1501 is located within the mobile communication module 150.

[0083]

[0091] The components of the wireless communication device will be described in detail below with reference to Figure 2a.

[0084]

[0092] (1) Processor 100

[0093] The processor 100 in this embodiment of the present application may include one or more processing units. For example, the processor 100 may include an application processor (AP) 110, a communications processor 1501 (e.g., a modem 15011), a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). The various processing units may be independent components or may be integrated into one or more processors. The controller may be the neural center and command center of a terminal device. The controller is capable of generating operation control signals based on instruction operation codes and time-series signals to complete control over instruction reading and instruction execution. In Figure 1, an example in which the communications processor 1501 is located within a mobile communications module 150 is used for illustrative purposes. In a particular implementation, the communication processor 1501 may alternatively be located within the processor 100.

[0085]

[0094] (2) Mobile communication module 150

[0095] The wireless communication function of the terminal device may be implemented by using antenna 1, antenna 2, mobile communication module 150, wireless communication module 140, communication processor 1501 (e.g., modem 15011), baseband processor, etc.

[0086]

[0096] Antennas 1 and 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the terminal device may be configured to cover one or more communication frequency bands. Different antennas may be further multiplexed to improve antenna availability. For example, antenna 1 may be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas may be used in combination with tuning switches.

[0087]

[0097] The mobile communication module 150 may provide a wireless communication solution used in terminal devices, including wireless communications such as 2G, 3G, 4G, and 5G. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 may receive electromagnetic waves via antenna 1, perform processing such as filtering and amplification on the received electromagnetic waves, and transmit the electromagnetic waves to the communication processor 1501 for demodulation. The mobile communication module 150 may also further amplify the signal modulated by the communication processing unit 1501 and convert the signal into electromagnetic waves for radiation from antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 (e.g., the communication processor 1501) may be located within the processor. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor may be located within the same component.

[0088]

[0098] (3) Communication processor 1501

[0099] The communication processor 1501 is, for example, a modem 15011. Modem 15011 is an abbreviation for modulator and demodulator and is referred to as modem in Chinese. Following the harmonic tone of the modem, modem 15011 is nicknamed "cat" and is an electronic device capable of implementing the modulation and demodulation functions required for communication. Modem 15011 typically includes a modulator and a demodulator. The modulator is configured to modulate the low-frequency baseband signal to be transmitted into a medium-to-high frequency signal. The demodulator is configured to demodulate the received electromagnetic signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to a baseband processor for processing. The low-frequency baseband signal is processed by the baseband processor and then transmitted to the application processor 110. In some embodiments, modem 15011 may be a standalone component. In some other embodiments, the modem 15011 may be independent of the processor and may be located within the same device as the mobile communication module 150 or another functional module.

[0089]

[0100] The modem 15011 may be a chip. For example, the modem 15011 may be an integrated circuit chip and have signal processing capabilities. In the implementation process, steps performed by the modem 15011 may be completed by using instructions in the form of hardware integrated logic circuits or software within the modem 15011.

[0090]

[0101] The application processor 110 and the communication processor 1501 may be integrated into the same wireless communication device or the same large chip (for example, a common SoC (system on a chip) chip in a mobile phone).

[0091]

[0102] (4) Wireless communication module 140

[0103] The wireless communication module 140 may provide solutions applicable to terminal devices for wireless communications including wireless local area networks (WLAN) (e.g., Wireless Fidelity (Wi-Fi) networks), Bluetooth® (BT), global navigation satellite systems (GNSS), frequency modulation (FM), near-field communication (NFC), and infrared (IR) technologies. The wireless communication module 140 may also be one or more components integrating at least one communication processing module. The wireless communication module 140 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering on the electromagnetic wave signal, and transmits the processed signal to processor 100. The wireless communication module 140 may further receive the signal to be transmitted from processor 100, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves for radiation via antenna 2.

[0092]

[0104] (5) Memory 130

[0105] Memory 130 may be further located within the processor and is configured to store instructions and data. In some embodiments, the memory within the processor is a cache. The memory may store instructions or data used or periodically used by the processor 100. When the processor needs to use an instruction or data again, it may retrieve the instruction or data directly from memory to avoid repeated access and reduce processor latency. Thus, it is possible to improve system efficiency.

[0093]

[0106] The wireless communication device may further include an external memory interface configured to connect to an external memory card, such as a microSD card, in order to expand the memory capacity of the terminal device.

[0094]

[0107] The internal memory can be configured to store computer executable program code, which includes instructions. The internal memory may include a program storage area and a data storage area. The program storage area may store the operating system, applications required by at least one function (e.g., audio playback function or image playback function), etc. Furthermore, the internal memory 121 may include high-speed random-access memory, or non-volatile memory, such as at least one magnetic disk storage device, flash memory, or universal flash storage (UFS). The processor 100 performs various functional applications and data processing of the terminal device by executing instructions stored in the internal memory 130 and / or instructions stored in memory located in the processor.

[0095]

[0108] (6) Communication interface 120

[0109] In some embodiments, the wireless communication device may include one or more communication interfaces 120. For example, the communication interface 120 may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, a universal serial bus (USB) interface, and / or similar interfaces.

[0096]

[0110] It should be understood that the various components shown in the figure may be implemented as hardware, software, or a combination of hardware and software including one or more signal processing, and / or application-specific integrated circuits. The terminal device shown in the figure is merely an example, and a terminal device may have more or fewer components than those shown in the figure, and two or more components may be combined, or different configurations of components may be used. Although not shown in Figure 2a, a terminal device may further include other components such as power management modules, buttons, and indicators. Further details are not described here.

[0097]

[0111] Based on the above, Figure 2b is an example of a schematic diagram of the structure of a wireless communication device according to an embodiment of the present application. The wireless communication device may be the wireless communication device of Figure 2a or the wireless communication device of Figure 1. Compared to the wireless communication devices of Figures 1 and 2a, the wireless communication device of Figure 2b may contain more or fewer components or modules than those shown in Figures 1 and 2a. As shown in Figure 2b, the wireless communication device may include an application processor 110. The application processor 110 is configured to run an operating system. The operating system layer 1101 may be located within the application processor 110. In this embodiment of the present application, at least one application, such as application 1, application 2, and application 3, may be further installed in the wireless communication device. These applications may, alternatively, be run by the application processor 110. The communication processor 1501 may run the communication protocol stack of the wireless communication device and is configured to receive and transmit data, etc.

[0098]

[0112] Regarding URSP, when a higher-layer system (e.g., operating system layer 1101) analyzes the original URSP code stream, it is difficult to modify the control layer code for certain types of features because the operating system of the wireless communication device is controlled by the system publisher. Therefore, each manufacturer is required to develop and maintain the URSP functionality themselves, and the protocol analysis code in operating system layer 1101 needs to be modified in synchronization with 3GPP protocol upgrades, which results in high development and maintenance costs. Furthermore, some small wireless communication devices, such as routers, do not have an operating system layer 1101, but only an application control layer, and basically do not have the ability to analyze the original URSP code stream, making it even more difficult to upgrade them in conjunction with 3GPP protocol upgrades. Therefore, currently, URSP functionality cannot be implemented in such communication devices.

[0099]

[0113] In this regard, this embodiment of the present application provides a solution for implementing URSP functionality by using a communication processor 1501, that is, for implementing URSP selection functionality during the establishment of a protocol data unit (PDU) session. Thus, if the communication processor in this embodiment of the present application is installed in a wireless communication device manufactured by each wireless communication device manufacturer, it is not necessary to incur costs in developing and maintaining URSP functionality in the operating system layer 1101. Furthermore, in the case of a wireless communication device that does not have an operating system, or whose operating system does not have the ability to perform decoding based on the original code stream corresponding to the URSP rules, the URSP functionality can be alternatively implemented by using the installed communication processor 1501. Moreover, according to the solution provided in this embodiment of the present application, the upper layer system (e.g., the operating system layer 1101) requires little to no modification, and does not require the provision of an additional intermediate layer between the upper layer system and the communication processor 1501.

[0100]

[0114] Based on the above, Figure 3 is an example of a schematic diagram of the structure of a wireless communication device according to an embodiment of the present application. The wireless communication device may be the wireless communication device of Figure 2b, or the wireless communication device of Figure 2a, or the wireless communication device of Figure 1. Compared with the wireless communication devices of Figures 1, 2a, and 2b, the wireless communication device shown in Figure 3 may include only a communication processor. As shown in Figure 3, the wireless communication device may include a communication processor, and the communication processor may include a processing circuit and an interface circuit. The interface circuit may be configured to input and output information. The processing circuit may be configured to execute a computer executable program, thereby executing an embodiment of the communication processor-side method provided in the embodiment of the present application.

[0101]

[0115] The processing unit may be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or another programmable logic device, transistor logic device, hardware component, or any combination thereof. The processor may implement or execute various exemplary logic blocks, modules, and circuits described in relation to the disclosures in this application. Alternatively, the processor may be a combination of processors that perform arithmetic functions, including, for example, a combination of one or more microprocessors, or a combination of a DSP and a microprocessor. The processing circuit may execute computer executable instructions stored in a memory module.

[0102]

[0116] An interface circuit may be a unit, module, or interface on a communication processor configured to transmit information. Alternatively, the function of an interface circuit may be performed by a transceiver module, transceiver, communication module, etc., within the communication processor. An interface circuit may be configured to receive signals from another device. For example, if the communication processor is implemented in the form of a chip, the communication processor is either an interface circuit used by the chip to receive signals from another chip or device, or an interface circuit used by the chip to transmit signals to another chip or device. An interface circuit may be, for example, a transceiver. Optionally, a transceiver may include a radio frequency circuit. An interface circuit may be, for example, an input / output interface, pin, or circuit.

[0103]

[0117] In yet another possible implementation, the processing circuit may invoke a computer executable program stored in a memory module, thereby executing an embodiment of the communication processor-side method provided in the embodiments of the present application. The memory module may be memory. Optionally, the memory module may be an in-chip memory module such as a register or cache, or it may be an out-of-chip memory module in the communication device, such as read-only memory (ROM), another type of static memory device capable of storing static information and static instructions, or random access memory (RAM).

[0104]

[0118] Specifically, the functions / implementation processes of the interface circuit and processing circuit in Figure 3 may be performed by the communication processor 1501 in the wireless communication device shown in Figure 2a or Figure 2b by calling computer executable instructions stored in memory. Alternatively, the functions / implementation processes of the processing circuit in Figure 3 may be performed by the communication processor 1501 in the wireless communication device shown in Figure 2a or Figure 2b by using computer executable instructions stored in memory, and the functions / implementation processes of the interface circuit in Figure 3 may be performed by the communication interface in the communication processor 1501 in the wireless communication device shown in Figure 2a or Figure 2b.

[0105]

[0119] The solutions provided in the embodiments of this application will be described in detail based on the above. Before that, in order to facilitate understanding of the embodiments of this application, the "user route selection policy" in this application will be described first.

[0106]

[0120] 3GPP defines user route selection policy rules (URSP, or abbreviated as URSP rules, or may be referred to as URSP rules; also, the target URSP rules in this specification may be referred to as target URSP rules, etc.). URSP rules may include rule precedence, traffic descriptors (TDs), and route selection descriptors (RSDs). A single URSP rule may include one traffic descriptor and one or more route selection descriptors.

[0107]

[0121] In this embodiment of the present application, the traffic descriptor may include at least one of the following: an application descriptor, an IP descriptor, a domain descriptor, a non-IP descriptor, a data network name (DNN), or connection capability. In this embodiment of the present application, the route selection descriptor may include at least one of the following: route selection descriptor preference, service and session continuity mode (SSC) selection, network slice selection, PDU session type selection, non-seamless offload instruction, access type preference, route selection validity criterion, time window, or location criterion.

[0108]

[0122] The contents of the URSP rule and the traffic descriptor are described below with reference to Table 1, and the contents of the route selection descriptor are described below with reference to Table 2. It should be noted that the contents of the URSP rule as defined in this embodiment of the present application are merely examples. As technology advances, the URSP rule may include additional information, or some components or parameters in the example may be removed; or other components or parameters may be added to the traffic descriptor, or some components or parameters in the traffic descriptor may be removed. The route selection descriptor may include additional components or parameters, or some components or parameters of the route selection descriptor in this example may be removed.

[0109] Table 1: User Route Selection Policies and Rules

[0110] [Table 1] TIFF0007886349000002.tif160170 Table 2: Route Selection Descriptors

[0111] [Table 2] TIFF0007886349000004.tif185128

[0123] Based on the above, Figures 4A and 4B are examples of schematic flowcharts of possible communication methods according to embodiments of the present application. As shown in Figures 4A and 4B, the method may be carried out by the wireless communication devices of Figures 2a, 2b, and 3. The wireless communication device may be the terminal device 10 or the access network device 20 in Figure 1, or it may be a chip such as, for example, a chip in the terminal device 10 or a chip in the access network device 20.

[0112]

[0124] In possible implementations, the wireless communication device includes only a communication processor, such as the wireless communication device shown in Figure 3.

[0113]

[0125] In another possible implementation, the wireless communication device may include an application processor and a communication processor, for example, the wireless communication device shown in Figure 2a or Figure 2b. The application processor is coupled to the communication processor. The application processor may be application processor 110 in Figures 2a and 2b, and the communication processor may be communication processor 1501 or modem 15011 in Figures 2a and 2b. The method may further include a network device, which may be core network device 30 in Figure 1.

[0114]

[0126] It should be noted that the session in this embodiment of the present application may be a session in multiple communication systems, for example, a PDU session in a 5G system, or a session in a future communication system architecture. In a future system architecture, the session may still use the name PDU session in 5G, or it may use a different name. This is not limited to this embodiment of the present application. To illustrate more clearly the solution provided in the embodiment of the present application, this embodiment of the present application uses an example where the session is a PDU session in a 5G system for illustrative purposes. If a different name is adopted for a future session, the name PDU session will be replaced accordingly with the different name.

[0115]

[0127] As shown in Figures 4A and 4B, the method includes the following steps.

[0116]

[0128] S401: The communication processor receives an original code stream distributed by a network device, which corresponds to at least one URSP rule corresponding to a wireless communication device.

[0117]

[0129] S402: The communication processor decodes the original code stream corresponding to the URSP rule to obtain at least one URSP rule and stores at least one URSP rule in memory.

[0118]

[0130] In possible implementations, the original code stream corresponding to the URSP rule may be included within the original code stream of the UE selection policy.

[0119]

[0131] S403: The communication processor returns a fourth response to the network device.

[0120]

[0132] The fourth response can indicate to network devices that the wireless communication device has successfully received the URSP rule.

[0121]

[0133] It should be noted that in this embodiment of the application, the communication processor acquires URSP rules in multiple ways. In addition to the solutions in S401 to S403, for example, URSP rules may be acquired in a pre-configured way or generated according to pre-configured rules. Steps S401 to S403 are not mandatory.

[0122]

[0134] In a possible implementation, a single URSP rule includes one traffic descriptor and at least one route selection descriptor. Alternatively, each URSP rule may have a URSP rule priority. The data being transmitted may match multiple URSP rules. In this case, the data being transmitted may be used sequentially based on the multiple URSP rule priorities.

[0123]

[0135] In a possible implementation, a traffic descriptor contains at least one parameter. For example, it may contain at least one parameter used to describe routing information. For example, a traffic descriptor may contain at least one of the following parameters: destination address parameter, data network parameter, application descriptor, or connection capability parameter.

[0124]

[0136] The destination address parameter may include at least one of the following parameters: domain descriptor, Internet Protocol IP descriptor, or non-IP descriptor. The data network parameter may include at least one of the following parameters: DNN, data network type, or access name. Non-IP descriptors may include 802.1Q C-TAG VID, 802.1Q S-TAG VID, 802.1Q C-TAG PCP / DEI, 802.1Q S-TAG PCP / DEI, Ethertype, etc.

[0125]

[0137] For the parameters included in the traffic descriptor in this embodiment of the present application, please refer to Table 1 above. Further details are not described here.

[0126]

[0138] In a possible implementation, a route selection descriptor includes at least one parameter, which may include, for example, a parameter that a PDU session requires to match. In a possible implementation, a parameter that a PDU session requires to match includes at least one of the following: a network parameter requested by the PDU session; a network slice parameter requested by the PDU session; or a session service parameter requested by the PDU session.

[0127]

[0139] Network parameters may include at least one of the following: PDU session type, data network name DNN, access type preference, or non-seamless offload instruction. Network slice parameters may include at least one of the following: network slice type, or network slice name. Session service parameters may include session service continuity (SSC) parameters.

[0128]

[0140] For parameters included in the route selection descriptor in this embodiment of the present application, please also refer to Table 2 above. Further details are not described here. Each route selection descriptor may further correspond to route selection descriptor priority. Thus, when multiple route selection descriptors are matched, the multiple route selection descriptors may be used sequentially during the start of a PDU session based on the priority of the multiple route selection descriptors.

[0129]

[0141] S404: The communications processor sends a first message to the application processor, the first message containing parameters for at least one traffic descriptor in at least one URSP rule.

[0130]

[0142] In a possible implementation, the first message includes at least one parameter of at least one traffic descriptor in at least one URSP rule. In another possible implementation, the first message includes all parameters of at least one traffic descriptor in at least one URSP rule.

[0131]

[0143] The first message may be an AT command, or of course, another command. The AT command set is a control protocol for controlling a modem, invented by Hayes, the inventor of the dial-up modem. AT stands for Attention. The protocol itself uses text. Each command begins with AT.

[0132]

[0144] The current documentation specifies an AT command profile, which is recommended for use in controlling mobile termination (MT) functions and network services from a terminal device (TE) via a terminal adapter (TA). The command prefix +C is reserved for digital cellular in ITU Recommendation V.250. The corresponding English description is given as follows:

[0145] “The present document specifies a profile of AT commands and recommends that this profile be used for controlling Mobile Termination (MT) functions and network services from a Terminal Equipment (TE) through Terminal Adapter (TA). The command prefix +C is reserved for Digital Cellular in ITU T Recommendation V.250.”

[0146] In a possible implementation, the first message is applicable to a 5G network and is used to transmit at least one traffic descriptor in at least one URSP rule (this may be understood as a function of the first message used to transmit a TD report). In this embodiment of the present application, the first message may be a newly defined AT command, for example, +C5GTDRPT;+CTDRPT;+CURSPRPT; or +C5GTD. In this embodiment of the present application, the first message may have multiple names, and is not limited to these.

[0133]

[0147] S405: The application processor determines the routing information parameters corresponding to the data to be transmitted.

[0134]

[0148] In possible implementations, if the wireless communication device is a mobile phone, routing parameters may be determined based on an application on the mobile phone initiated by the user. In another possible implementation, if the wireless communication device is a router, routing parameters may be determined based on the data to be transmitted. Before performing data transmission with the network (in other words, before the data services of the wireless communication device are activated), the wireless communication device is required to establish a network connection. The connection may be a PDU session connection. A PDU session connection may be a newly established PDU session connection or a previously established PDU session connection. This part is described in detail below and is not described in detail here.

[0135]

[0149] In this embodiment of the present application, the routing information parameter includes at least one of the following parameters: a destination address parameter for the data to be transmitted, a data network parameter corresponding to the data to be transmitted, an application descriptor corresponding to the data to be transmitted, or a connection capability parameter corresponding to the data to be transmitted.

[0136]

[0150] The destination address parameter may include at least one of the following parameters: a domain descriptor corresponding to the data to be transmitted, an IP descriptor corresponding to the data to be transmitted, or a non-IP descriptor corresponding to the data to be transmitted. The data network parameter may include at least one of the following parameters: a DNN, a data network type, or an access name. The domain descriptor may be a standard expression as a domain name that meets the criteria or a fully qualified domain name (FQDN) of the target. The IP descriptor may be a target IP 3-tuple (such as an IP address or IPv6 network prefix and port number).

[0137]

[0151] S406: The application processor determines whether at least one of the received traffic descriptors contains a traffic descriptor that matches a pre-configured condition. The pre-configured condition includes: the parameters in the traffic descriptor matching the routing information parameters.

[0138]

[0152] If no traffic descriptors matching the pre-configured conditions exist, S407 is executed.

[0139]

[0153] If a traffic descriptor exists that matches the pre-configured conditions, S408 is executed.

[0140]

[0154] S407: The procedure is complete.

[0141]

[0155] In this embodiment of the present application, in possible implementations, all parameters included in a traffic descriptor that meets a predefined condition are the same as the parameters in the routing information parameters. For example, a traffic descriptor may include only a destination address parameter, while the routing information parameters may include both a destination address parameter and a data network parameter. If the destination address parameter in the traffic descriptor is the same as the destination address parameter in the routing information parameters, then the traffic descriptor meets the predefined condition. In another example, a traffic descriptor may include both a destination address parameter and a data network parameter, while the routing information parameters may include only a destination address parameter. Even if the destination address parameter in the traffic descriptor is the same as the destination address parameter in the routing information parameters, the traffic descriptor is determined not to meet the predefined condition because the data network parameter in the traffic descriptor does not match the data network parameter in the routing information parameters.

[0142]

[0156] In a possible implementation, if the application processor determines in S406 that at least one traffic descriptor exists within the received traffic descriptor, and all parameters contained in the traffic descriptor are the same as some or all of the parameters in the routing information parameters, the application processor may further query whether an active PDU session (i.e., an established PDU session connection) exists. The PDU session matches the parameters in the traffic descriptor (i.e., the PDU session is a PDU session that matches the route selection descriptor, and the parameters in the traffic descriptor corresponding to the route selection descriptor are the same as the parameters in the traffic descriptor). If an active PDU session exists, the data may be transmitted using the active PDU session. If no active PDU session exists, S407 may be performed.

[0143]

[0157] In possible implementations, the application processor may perform a preliminary screening so that it determines that a traffic descriptor corresponding to the routing information parameters exists within the URSP rules distributed by the network before sending the first request. In another possible implementation, if it is found that a traffic descriptor matching the routing information parameters does not exist within the URSP rules distributed by the network, the original solution may be used. Specifically, after receiving the session activation request, the communication processor directly initiates the session to the network without querying the route selection descriptor. However, the parameters in the route selection descriptor are no longer used as dialing parameters in the session. In yet another possible implementation, if a traffic descriptor matching the routing information parameters does not exist within the URSP rules distributed by the network, the PDU session may be determined to have not been successfully activated.

[0144]

[0158] It should be noted that S404 and S406 are not mandatory. If S404 or S406 are present, the application processor may perform a preliminary screening, and if it determines that a TD matching the first parameter exists, the application processor sends the first request. If S404 or S406 are not performed, S408 may alternatively be performed after the application processor has directly obtained the first parameter.

[0145]

[0159] S408: The application processor sends a first request to the communication processor. The first request is used to query the route selection descriptor, which includes route information parameters corresponding to the data to be transmitted, and the route selection descriptor matches the route information parameters.

[0146]

[0160] Accordingly, the communication processor receives the first request.

[0147]

[0161] In this embodiment of the present application, after receiving a first request, the communications processor may query whether the target URSP rule exists in the stored URSP rules and whether the traffic descriptor in the target URSP rule matches the routing information parameters. In possible implementations, a traffic descriptor matching the routing information parameters means that all or some of the parameters contained in the traffic descriptor are the same as those in the routing information parameters. See above for relevant examples. Further details are not provided here.

[0148]

[0162] The first request in this embodiment of the present application may be an AT command, or of course another command. In possible implementations, the first request is applicable to a 5G network and is used to query a route selection descriptor (used to query an RSD). In this embodiment of the present application, the first request may be a newly defined AT command, for example:+C5GRSDQRY;+C5GURSPQRY:+CURSPQRY;+CQRSD;+C5GQRSD; or+C5GRURSP. In this embodiment of the present application, the first request may have multiple names, and is not limited to these.

[0149]

[0163] S409: The communication processor finds the target URSP rule.

[0150]

[0164] S410: The communications processor returns a first response to the application processor, which may include at least one parameter of at least one route selection descriptor in the target URSP rule.

[0151]

[0165] In a possible implementation, the first response may contain all parameters in at least one route selection descriptor within the target URSP rule.

[0152]

[0166] For details regarding the parameters included in the route selection descriptor, please refer to the information above. Further details will not be explained here.

[0153]

[0167] In this embodiment of the present application, there may be one or more target URSP rules discovered. When there are multiple target URSP rules, at least one parameter in at least one route selection descriptor of at least one of the multiple target URSP rules may be returned to the application processor by using one first response, or at least one parameter in at least one route selection descriptor of each of the multiple target URSP rules may be returned to the application processor by using multiple first responses. For example, one first response may carry all the parameters in one route selection descriptor within one target URSP rule.

[0154]

[0168] In possible implementations, when multiple target URSP rules exist, the communications processor can further transmit the priority of the multiple target URSP rules to the application processor, and as a result, the application processor uses the route selection descriptors in the target URSP rules based on priority.

[0155]

[0169] In possible implementations, the first response may further carry the priority of at least one route selection descriptor in the target URSP rule. In this way, the application processor can sequentially use multiple route selection descriptors based on the priority of those descriptors.

[0156]

[0170] In another possible implementation, at S410, the communications processor may further query whether an activated PDU session (i.e., an established PDU session connection) exists, where the PDU session matches at least one route selection descriptor in the target URSP rule (i.e., the PDU session matches parameters in at least one route selection descriptor in the target URSP rule). If information about an active PDU session exists, in a possible implementation, the information about the activated PDU session may be carried in the first response and sent to the application processor, or the information about the activated PDU session may be returned to the application processor using a separate message. In this way, the application processor can choose to use the activated PDU session directly or to re-establish the PDU session.

[0157]

[0171] S411: The application processor sends a third request to the communications processor. The third request is used to activate the PDU session. The third request may include at least one parameter in the route selection descriptor.

[0158]

[0172] In S409, after finding at least one route selection descriptor within at least one target URSP rule, the application processor may sequentially select and use route selection descriptors based on the URSP rule priority and route selection descriptor priority, and may carry the parameters of the currently selected route selection descriptor in the third request (which may be all parameters, or at least one parameter, within the selected route selection descriptor). The parameters within the route selection descriptor carried in the third request may be referred to as dialing parameters. The PDU session connection then established based on the third request matches the dialing parameters carried in the third request.

[0159]

[0173] The third request may be an AT command used to activate the PDU (used to activate a 5GS PDU session), or of course another command, such as +CGACT.

[0160]

[0174] In possible implementations, in this embodiment of the present application, after receiving a third request, the application processor may choose to query whether an active PDU session (i.e., an established PDU session connection) exists, where the PDU session matches at least one route selection descriptor carried in the third request (i.e., the PDU session matches the parameters of the route selection descriptor carried in the third request). If an active PDU session exists, in possible implementations, information about the active PDU session may be sent to the application processor. In this way, the application processor can choose to use the activated PDU session directly or to re-establish the PDU session. Indeed, if a historical PDU session is queryed when the first response is returned in S410, no query is performed after S411. Alternatively, if the application processor queries in S406 whether a matching historical PDU session exists, queries may not be required in S410 and S411.

[0161]

[0175] S412: The communications processor sends a second request to the network device, which is used to activate a PDU session, and which includes at least one parameter in the route selection descriptor.

[0162]

[0176] It should be noted that S410 and S411 are not mandatory. If S411 is present, in possible implementations, the parameters in the route selection descriptor that may be carried by the communication processor in the second request are the parameters in the route selection descriptor that are carried in the third request.

[0163]

[0177] In yet another possible implementation, if S410 and S411 are not present, the parameters of the route selection descriptor carried in the second request may be the parameters of a route selection descriptor that were sequentially selected based on the priority of the URSP rule and the priority of the route selection descriptor. The second request may carry all or at least one parameter in the selected route selection descriptor.

[0164]

[0178] In possible implementations, the second request may be a PDU session establishment request, which may be written as a PDU session establishment request in English. The second request is used to request the establishment or activation of a PDU session connection to the network, and the PDU session connection matches the parameters in the route selection descriptor carried in the second request.

[0165]

[0179] S413: The communications processor receives a second response sent by the network device, the second response indicating that the PDU session has been successfully activated.

[0166]

[0180] In this embodiment of the present application, the second response may be a PDU session establishment accept, or it may be written in English as PDU session establishment accept.

[0167]

[0181] S414: The communications processor returns a third response to the application processor, which indicates that the PDU session has been successfully activated.

[0168]

[0182] It should be noted that if the response received after the communication processor sends a second request in S412 indicates that the PDU session failed to be activated, a route selection descriptor may be selected (for example, based on the priority of the target URSP rule and the priority of the route selection descriptor in the target URSP), and the second request may be resent to reactivate the PDU session. The second request may be sent repeatedly until the PDU session is successfully established or until all route selection descriptors in all discovered target URSP rules have been used and all PDU sessions have failed to be established. The second request may be triggered by a third request resent by the application processor, or after a message indicating that the PDU session failed to be activated is received.

[0169]

[0183] Currently, the protocol does not specify the use of URSP information. Only two relevant AT commands are defined in the 3GPP 27.007 protocol. The modem reports UE selection policy information distributed by the network to the upper layer system in the form of an original code stream by using the + CRUEPOLICY command. The upper layer system decodes the original code stream of the UE selection policy and sends the + CSUEPOLICY command to the modem. The modem then forwards the code stream to the network devices. However, vendors develop and maintain the upper layer system by using URSP functionality, which is costly. Also, the upper layer system of some wireless communication devices does not have the ability to decode the original code stream corresponding to URSP rules. Based on this, in this embodiment of the present application, after receiving a first request containing routing information parameters, the communication processor can add a routing selection descriptor to a second request that has been sent, so that the established PDU session can conform to URSP functionality. Furthermore, since the URSP function of the wireless communication device is implemented by using a communication processor, the vendor of the wireless communication device does not need to develop and maintain a higher-layer system to implement the URSP function, thereby reducing the vendor's costs. Also, for wireless communication devices that do not have the ability to decode the original code stream corresponding to the URSP rule, the URSP function can be implemented by simply installing a communication processor, thereby reducing the complexity of implementing the URSP function for wireless communication devices with limited capabilities. The solution provided in this embodiment of the present application may be further applicable to products that require optimization of the PDU session establishment procedure (which may also be referred to as the data service activation procedure) based on product characteristics, and that have little impact on the data service processing procedure of the original product.

[0170]

[0184] Based on the solutions shown in Figures 4A and 4B, an example of the first request syntax is shown below using Table 3. The first column contains the parameters included in the first request. The second column contains the values ​​returned by the communication processor after it receives the first request. Table 4 shows an example of the meaning of the parameters in Table 3. In Tables 3 and 4, an example is used in which the first request is named +C5GRSDQRY. In a real application, the first request may have a different name.

[0171] Table 3 +C5GRSDQRY Command Syntax Description

[0172] [Table 3] Table 4 +C5GRSDQRY Command Parameter Description

[0173] [Table 4] TIFF0007886349000007.tif192128TIFF0007886349000008.tif128170

[0185] Based on the above, Figures 5A and 5B are examples of schematic flowcharts of another possible communication method according to embodiments of the present application. As shown in Figures 5A and 5B, the method may be carried out by the wireless communication device shown in Figures 2a and 2b. The wireless communication device may be the terminal device 10 or the access network device 20 in Figure 1, or it may be a chip such as, for example, a chip in the terminal device 10 or a chip in the access network device 20.

[0174]

[0186] The wireless communication device includes an application processor and a communication processor. The application processor is coupled to the communication processor. The application processor may be the application processor 110 in Figures 2a and 2b, and the communication processor may be the communication processor 1501 or modem 15011 in Figures 2a and 2b. The method may further include a network device, which may be the core network device 30 in Figure 1.

[0175]

[0187] As shown in Figures 5A and 5B, the method includes the following steps.

[0176]

[0188] For steps S401 to S407 in Figures 5A and 5B, please refer to steps S401 to S407 in Figures 4A and 4B. If it is determined in S406 in Figures 5A and 5B that a traffic descriptor matching the pre-configured conditions exists, S501 is executed. As with the contents of Figures 4A and 4B, steps S401 to S407 are optional and not required.

[0177]

[0189] S501: The application processor sends a first request to the communications processor. The first request includes routing information parameters corresponding to the data to be transmitted, and the routing selection descriptor matches the routing information parameters. The first request is used to activate the PDU session. In other words, the first request is used to query the routing selection descriptor and is further used to activate the PDU session.

[0178]

[0190] Accordingly, the communication processor receives the first request.

[0179]

[0191] In this embodiment of the present application, after receiving a first request, the communications processor may query whether the target URSP rule exists in the stored URSP rules and whether the traffic descriptor in the target URSP rule matches the routing information parameters. In possible implementations, a traffic descriptor matching the routing information parameters means that all or some of the parameters contained in the traffic descriptor are the same as those in the routing information parameters. See above for relevant examples. Further details are not described here.

[0180]

[0192] The first request in this embodiment of the present application may be an AT command. For details of the AT command, please refer to the parameters described above.

[0181]

[0193] In possible implementations, the first request is applicable to a 5G network and is used to activate a route selection descriptor (used to activate a 5GS PDU session). In this embodiment of the present application, the first request may be a newly defined AT command, for example: +CACTPDU; +CPSDIAL; +CPDUACT; +CPDUEST; or +CPDUCONN. In this embodiment of the present application, the first request may have multiple names, and is not limited to these.

[0182]

[0194] S502: The communication processor discovers the target URSP rule.

[0183]

[0195] In another possible implementation, S503 may be executed directly after S502.

[0184]

[0196] In another possible implementation, at S502, the communications processor may further query whether an activated PDU session (i.e., an established PDU session connection) exists, where the PDU session matches at least one route selection descriptor in the target URSP rule (i.e., the PDU session matches parameters in at least one route selection descriptor in the target URSP rule). If an activated PDU session exists, in a possible implementation, information about the activated PDU session may be returned to the application processor, and a message indicating that the PDU session was successfully activated (e.g., a third response at S414) is sent directly to the application processor. After receiving the message, the application processor may transmit data by using the activated PDU session. In this scenario, the communications processor is not required to perform S503 and S413. Furthermore, if the activated PDU session does not match at least one route selection descriptor in the target URSP rule, S503 may still be executed.

[0185]

[0197] S503: The communications processor sends a second request to the network device, which is used to activate a PDU session, and which includes at least one parameter in the route selection descriptor.

[0186]

[0198] The parameters of the route selection descriptor carried in the second request may be parameters in a route selection descriptor that is sequentially selected by the communication processor based on the priority of the discovered target URSP rule and the priority of the route selection descriptor. The second request may carry all or at least one parameter in the selected route selection descriptor.

[0187]

[0199] In possible implementations, the second request may be a PDU session establishment request, which may be written as a PDU session establishment request in English. The second request is used to request the establishment or activation of a PDU session connection to the network, and the PDU session connection matches the parameters in the route selection descriptor carried in the second request.

[0188]

[0200] S413 and S414 may be executed after S503. For relevant details, please refer to S413 and S414 in Figures 4A and 4B. Further details will not be explained here.

[0189]

[0201] In the solutions shown in Figures 5A and 5B, the application processor knows that it will only send the first request, and then the communications processor will complete the URSP rule query and PDU activation (or the communications processor will trigger data service dialing). In this way, changes to the application processor can be minimized, thereby laying the foundation for further enhancing the competitiveness of the communications processor.

[0190]

[0202] Based on the solutions shown in Figures 5A and 5B, an example of the first request syntax is shown below using Table 5. The first column contains the parameters included in the first request. The second column contains the values ​​returned by the communication processor after it receives the first request. For the meaning of the parameters included in the first request in Table 5, please refer to the contents of Table 4. In Table 5, an example is used where the first request is named +CACTPDU. In actual applications, the first request may have a different name.

[0191] Table 5 + CACTPDU Command Syntax Description

[0192] [Table 5]

[0203] Based on S404 in the solutions shown in Figures 4A and 4B and Figures 5A and 5B, an example of the first message syntax is shown below using Tables 6 and 7. The first column in Table 6 contains the parameters included in the first message. The second column contains the values ​​returned by the communication processor after it receives the first request. Table 7 shows an example of the meaning of the parameters included in the first column of Table 6. In Tables 6 and 7, an example is used where the first request is +C5GTDRPT. In a real application, the first request may have a different name.

[0193] Table 6: Description of the +C5GTDRPT command syntax

[0194] [Table 6] Table 7: Description of the +C5GTDRPT command parameter

[0195] [Table 7]

[0204] The terms “system” and “network” can be used interchangeably in the embodiments of this application. “At least one” means one or more, and “multiple” means two or more. The terms “and / or” describe a relationship between related subjects, indicating that three relationships may exist. For example, A and / or B may indicate the following cases: only A exists, both A and B exist, or only B exists, where A and B may be singular or plural. The letter “ / ” generally indicates an “or” relationship between related subjects. At least one of the following items (parts) or a similar expression refers to any combination of these items, including any combination of singular or plural items (parts). For example, at least one of a, b, or c may indicate: a, b, c, ab, ac, bc, or abc, where a, b, and c may be singular or plural.

[0196]

[0205] Furthermore, unless otherwise stated, ordinal numbers such as “First” and “Second” in the embodiments of this application are used to distinguish between multiple subjects, and not to limit the order, chronological order, priority, or importance of the multiple subjects. For example, the first request and the second request are used merely to distinguish between different requests and do not indicate different priorities, different importance, etc., between the two requests.

[0197]

[0206] It should be understood that the division of the communication device into the aforementioned units is merely a logical functional division. In actual implementation, all or part of the units may be integrated into a single physical entity or they may be physically separated.

[0198]

[0207] According to the methods provided in the embodiments of this application, this application further provides a computer program product, which includes computer program code. When the computer program code is executed on a computer, the computer becomes capable of performing any of the methods in the embodiments.

[0199]

[0208] According to the methods provided in the embodiments of the present application, the present application further provides a computer-readable storage medium. The computer-readable medium stores program code. When the program code is executed on a computer, the computer becomes capable of performing any of the methods in the embodiments.

[0200]

[0209] All or part of the embodiments described above may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded into a computer and executed, the procedures or functions according to the embodiments of this application occur, in whole or in part. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired means (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless means (e.g., infrared, radio, or microwave). Computer-readable storage media may be any available media accessible by a computer, or a data storage device such as a server or data center that integrates one or more available media. Available media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), semiconductor media (e.g., solid-state drives (SSDs)), etc.

[0201]

[0210] The network device in the aforementioned embodiment of the apparatus corresponds to the network device in the embodiment of the method. The corresponding module or unit performs the corresponding steps. For example, a communication unit (transceiver) performs the receiving step or the transmitting step in the embodiment of the method, and steps other than the transmitting and receiving steps may be performed by a processing unit (processor). For the functions of a particular unit, refer to the corresponding embodiment of the method. There may be one or more processors.

[0202]

[0211] As used in this specification, terms such as “component,” “module,” and “system” are used to indicate computer-related entities, hardware, firmware, combinations of hardware and software, software, or running software. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated by the use of diagrams, both a computing device and an application running on a computing device may be components. One or more components may reside within a process and / or an execution thread, and components may be located on one computer and / or distributed across two or more computers. Furthermore, these components may be executed from various computer-readable media that store various data structures. For example, components may communicate based on signals having one or more data packets, for example, by using local and / or remote processes (e.g., data from a local system, data from two components interacting with another component in a distributed system, and / or data over a network such as the Internet interacting with other systems by using signals).

[0203]

[0212] A person skilled in the art will be able to recognize, in combination with the illustrative logical blocks described in the embodiments disclosed herein, that a step may be performed by electronic hardware, or by a combination of computer software and electronic hardware. Whether the function is performed by hardware or software depends on the specific application and design constraints of the technical solution. A person skilled in the art may use various methods to perform the described function for each specific application, but it should not be considered that such implementation goes beyond the scope of this application.

[0204]

[0213] For the purpose of a simple and concise explanation, it will be readily apparent to those skilled in the art that the detailed operating processes of the aforementioned systems, apparatus, and units should be referred to in the corresponding processes in the embodiments of the methods described above. Further details are not described here.

[0205]

[0214] It should be understood that, in some embodiments provided in this application, the systems, apparatus, and methods disclosed may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementations. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. Furthermore, the mutual coupling or direct coupling or communication connection indicated or discussed may be implemented by using some interfaces. Indirect coupling or communication connection between apparatus or units may be implemented electronically, mechanically, or in other forms.

[0206]

[0215] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units; in other words, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected based on the actual requirements in order to achieve the objectives of the solution of the embodiment.

[0207]

[0216] Furthermore, the functional units in the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0208]

[0217] When a function is implemented in the form of a software function unit and sold or used as an independent product, the function may be stored on a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be implemented in the form of a software product, either in essence, in part with respect to the prior art, or in part with respect to the technical solution. A computer software product is stored on a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0209]

[0218] The foregoing description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Any modifications or substitutions readily apparent to a person skilled in the art within the scope of the technical scope disclosed in the present application shall fall within the scope of protection of the present application. Accordingly, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. A wireless communication device including a communication processor and an application processor, wherein: The communication processor is configured to receive a first AT command transmitted by the application processor, the first AT command being used to query a route selection descriptor, and the first AT command including a first parameter; The communication processor is configured to send a first response to the application processor, the first response comprising at least one parameter of at least one route selection descriptor in a target user route selection policy URSP rule, the at least one route selection descriptor in the target URSP rule matching the first parameter, the first parameter being the same as a parameter included in a traffic descriptor in the target URSP rule, the route selection descriptor being the route selection descriptor in the target URSP rule; and A wireless communication device wherein the communication processor is configured to send a second request to a network device, the second request is used to establish a session, and the second request includes at least one parameter in the route selection descriptor.

2. In the wireless communication device according to claim 1, the first parameter is the following parameter: The destination address and parameters of the data to be transmitted; Data network parameters corresponding to the data to be transmitted; An application descriptor corresponding to the data to be transmitted; or Connection capability parameters corresponding to the data to be transmitted; A wireless communication device including at least one of the following.

3. In the wireless communication device according to claim 1, the traffic descriptor has the following parameters: Destination address parameters; Data network parameters; Application descriptor; or Connection capability parameters; A wireless communication device including at least one of the following.

4. In the wireless communication device according to claim 2, the destination address parameter is the following parameter: A domain descriptor corresponding to the data to be transmitted; An Internet Protocol IP descriptor corresponding to the data to be transmitted; or A non-IP descriptor corresponding to the data to be transmitted; A wireless communication device including at least one of the following.

5. In the wireless communication device according to any one of claims 1 to 4, the parameters in the route selection descriptor are: Network slice parameters; Data network name DNN; or Session type; Wireless communication devices, including those mentioned above.

6. In the wireless communication device according to claim 5, the parameters of the network are the following parameters: Session type; Data network name DNN; Access type priority; or Non-seamless off-road instructions; A wireless communication device including at least one of the following.

7. A wireless communication device according to any one of claims 1 to 6, wherein the first AT command is further used to activate the session.

8. In the wireless communication device according to claim 7, the first AT command is: +CACTPDU; +CPSDIAL; +CPDUACT; +CPDUEST; or +CPDRCONN A wireless communication device including at least one of the following.

9. In the wireless communication device according to any one of claims 1 to 8, the communication processor further comprises: A wireless communication device having an interface circuit configured to return a first response to the application processor after receiving the first AT command transmitted by the application processor and before sending the second request to the network device, wherein the first response includes the at least one parameter in the route selection descriptor.

10. In the wireless communication device according to claim 9, the first AT command is: +C5GRSDQRY; +C5GURSPQRY; +CURSPQRY; +CQRSD; +C5GQRSD; or +C5GRURSP A wireless communication device including at least one of the following.

11. A wireless communication device according to claim 10, wherein the first response further includes the priority of the route selection descriptor.

12. In the wireless communication device according to claim 10 or 11, after returning the first response and before sending the second request to the network device, the communication processor further: A wireless communication device configured to receive a third request transmitted by the application processor, the third request being used to activate the session, and the third request including the at least one parameter in the route selection descriptor.

13. A wireless communication device according to any one of claims 1 to 12, wherein the second request is a protocol data unit (PDU) session establishment request.

14. A wireless communication device according to any one of claims 1 to 13, further comprising: The communication processor is configured to receive, via an interface circuit, at least one URSP rule distributed by the network device, which corresponds to the wireless communication device, and the URSP rule in the at least one URSP rule includes a traffic descriptor and at least one route selection descriptor; and A wireless communication device wherein the communication processor is configured to send a first message to the application processor, the first message comprising parameters of at least one traffic descriptor in at least one URSP rule.

15. In the wireless communication device according to claim 14, the first message is: +C5GTDRPT; +CTDRPT; +CURSPRPT; or +C5GTD A wireless communication device including at least one of the following.

16. A wireless communication device according to claim 14 or 15, further comprising the application processor, wherein the communication processor is coupled to the application processor, and the application processor is specifically: The system is configured to send the first AT command when it is determined that a traffic descriptor matching a pre-configured condition exists in at least one of the received traffic descriptors. The aforementioned pre-configured conditions include: a wireless communication device in which the parameters of the traffic descriptor match the first parameters.

17. A communication method applicable to a wireless communication device including a communication processor and an application processor, wherein the communication method is performed by the communication processor on the following operations: A step of receiving a first AT command transmitted by the application processor, wherein the first AT command is used to query a route selection descriptor and the first AT command includes a first parameter; A step of sending a first response to the application processor, wherein the first response includes at least one parameter of at least one route selection descriptor in a target user route selection policy URSP rule, the at least one route selection descriptor in the target URSP rule matches the first parameter, the first parameter is the same as a parameter included in a traffic descriptor in the target URSP rule, and the route selection descriptor is a route selection descriptor in the target URSP rule; and A step of sending a second request to a network device, wherein the second request is used to establish a session, and the second request includes at least one parameter in the route selection descriptor; Methods that include...

18. In the method according to claim 17, the first parameter is the following parameter: The destination address and parameters of the data to be transmitted; Data network parameters corresponding to the data to be transmitted; An application descriptor corresponding to the data to be transmitted; or Connection capability parameters corresponding to the data to be transmitted; A method that includes at least one of the following.

19. In the method according to any one of claims 17 to 18, the traffic descriptor has the following parameters: Destination address parameters; Data network parameters; Application descriptor; or Connection capability parameters; A method that includes at least one of the following.

20. In the method according to any one of claims 17 to 19, the parameters in the route selection descriptor are: Network slice parameters; Data network name DNN; or Session type; Methods that include...

21. In the method according to claim 20, the parameters of the network are the following parameters: Session type; Data network name DNN; Access type priority; or Non-seamless off-road instructions; A method that includes at least one of the following.

22. A method according to any one of claims 17 to 21, wherein the first AT command is further used to activate the session.

23. In the method according to claim 22, the first AT command is: +C5GRSDQRY; +C5GURSPQRY; +CURSPQRY; +CQRSD; +C5GQRSD; or +C5GRURSP A method that includes at least one of the following.

24. The method according to claim 17, wherein the first response further includes the priority of the route selection descriptor.

25. In the method according to any one of claims 17 to 24, before receiving a first AT command transmitted by an application processor, the method further: A step of receiving at least one URSP rule distributed by the network device that corresponds to the wireless communication device, wherein the URSP rule in the at least one URSP rule includes a traffic descriptor and at least one route selection descriptor; and A step of sending a first message to the application processor, wherein the first message includes parameters of at least one traffic descriptor in at least one URSP rule; Methods that include...

26. The method according to claim 25, wherein the wireless communication device further includes the application processor, and the method further: The application processor includes the step of sending the first AT command if it determines that a traffic descriptor that matches a pre-configured condition exists in at least one of the received traffic descriptors; The aforementioned pre-configured condition is a method comprising: the parameter of the traffic descriptor matching the first parameter.

27. A communication device including a processor and memory: The memory is configured to store program instructions; and A communication device wherein the processor is configured to execute the program instructions stored in the memory to perform the method according to any one of claims 17 to 26.

28. A communication device including a processor and interface circuitry: The interface circuit is configured to access memory, which stores program instructions; and A communication device wherein the processor is configured to access the memory by using the interface circuit and execute the program instructions stored in the memory to perform the method according to any one of claims 17 to 26.

29. A computer-readable storage medium, wherein the computer-readable storage medium stores program code, and when the program code is executed by a computer, the method according to any one of claims 17 to 26 is performed.

30. A chip system comprising a communication interface and a processor, wherein the communication interface is configured to input and / or output information, and when the processor is operating, the method according to any one of claims 17 to 26 is performed.

31. A computer program wherein, when program code contained in the computer program is executed by a computer, the method according to any one of claims 17 to 26 is executed.

Images